Custom Query (7259 matches)
Results (94 - 96 of 7259)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#4831 | notabug | ui.sortables serialize function returns object | ||
Description |
I've noticed that in the 1.8a1 ui sortables, the serialize method seems to return an object instead of a string. Inside the ui.sortable code, doing a alert(typeof(str.join('&'))); before the return shows 'string', but doing the same for the return from the actual .sortable("serialize) method shows 'object'. |
|||
#4993 | worksforme | ui.sortable option helper (clone) doesn't work | ||
Description |
$('sth').sortable ({
}); seems not to work. There is no cloned helper to drag. |
|||
#11250 | duplicate | ui.sortable no longer works with different stacking contexts (1.11.2 regression) | ||
Description |
Hi there, I recently updated to jquery-ui 1.11.2 and noticed a weird new behaviour when dragging a draggable element into a sortable container when the sortable container is in a different stacking context. Basically, what happens is the draggable element gets "stuck" inside the sortable container, and it's position glitches out if you attempt to drag it outside the container. I'm not 100% sure why this happens, but it seems to be related to dragging an item from one stacking context to a next. Steps to reproduce are included in the following fiddles:
Note that this only seems to happen when the sortable container is in a different stacking context (in the examples above, I'm using two fixed position divs). After a bit of debugging, it seems to be related to how the "clone" helper is moved around the DOM. When the clone enters the sortable container, it gets added to the sortable, which causes it to render within the new stacking context. Beyond the visual annoyance (especially if the sortable container has overflow: hidden), the positioning of the draggable element goes crazy... |