Skip to main content

Search and Top Navigation

#7407 closed bug (invalid)

Opened May 20, 2011 07:34PM UTC

Closed November 23, 2012 08:52AM UTC

Cancel and event queue interact badly on IE

Reported by: jdmarshall Owned by: jdmarshall
Priority: minor Milestone: 2.0.0
Component: ui.sortable Version: 1.8.13
Keywords: Cc:
Blocked by: Blocking:

I have a sortable list with elements that get marked as unsortable until the changes have been saved on the server.

On IE, either because of differences in the event queue or just the slowness of refreshPositions, seems to queue up mouse drag events, so that a drag operation following another gets honored even though it gets ignored on other browsers.

What I suspect is happening is that on drag start, the positions get updated before the 'cancel' rule is applied. I think perhaps cancel should trump refreshPositions, no?

item.sortable( { cancel: '.inProgress', stop: function(event, ui) { saveChanges(); } });

Attachments (0)
Change History (3)

Changed October 11, 2012 02:55PM UTC by scottgonzalez comment:1


Changed November 08, 2012 08:40PM UTC by mikesherov comment:2

owner: → jdmarshall
status: newpending

Thanks for taking the time to contribute to the jQuery UI project! Please provide a complete reduced test case on jsFiddle to help us assess your ticket.

Additionally, be sure to test against the git version of both jQuery UI and jQuery to ensure the issue still exists. To get you started, use this boilerplate: Open the link and click to "Fork" (in the top menu) to get started.

Changed November 23, 2012 08:52AM UTC by trac-o-bot comment:3

resolution: → invalid
status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!