Hi Paul, it doesn't happen instantly, and not always. In my use of the ui.sortable a few additional dom operations take place, it seems like they favour the premature abort of the sorting. But it happens also without these additional dom operations.
This is in fact weird, as it seems not very predictable. But on further testing, it seems, that only a single event has the wrong button property, events later on have event.button==1 again. This problem has also been reported earlier by others, but without any solution. Checking the "stickiness" of the draggable, the behaviour of IE8 has not improved since IE7. Taking the "IE mouseup check" out of the code, will solve the problem of the unwanted sort stopping, but in case of a mouseup outside the browser window the sorting will continue until the next click. There seems to be no easy solution to both problems. Tobias Paul Bakaus schrieb: > Hi Tobias, > > that's weird. Could you explain what you did to cause the mouseUp, or > is it random / directly > after grabbing it? > > The check in question prevents "stickiness" of the draggable when you > grab the draggable, > drag it out of the window, and then (while holding the mouse button > pressed), dragging in > again. Internet Explorer usually stops the event flow when being in an > Area it can't drag, > as opposed to Firefox for instance, where the mouse coordinates are > negative when you > drag out of the viewport. > > Though 0 as property seems to be an IE8 bug, it's possible that they > fixed the outside > event propagation issue, so maybe that check isn't needed anymore. > > Can you check if that's the case? > > Thanks, > Paul > > On Mon, Aug 3, 2009 at 9:39 AM, tobirius <[email protected] > <mailto:[email protected]>> wrote: > > > Hi List, > > I'm experiencing problems with IE8 and ui.sortable. The sorting stops > even though the mouse-button is still pressed. I've looked through the > code and think this is caused in the _mouseMove function of ui.mouse. > > // IE mouseup check - mouseup happened when mouse was out of window > if ($.browser.msie && !event.button) { > return this._mouseUp(event); > } > > In this part, the button property of the mousemove-event in IE8 is 0, > even though the mouse-button is still pressed, and the _mouseUp > function is triggered. > > I would consider this as a bug in IE8, but what can you do? > > Has anybody an idea for a workaround? > > Tobias > > > > > -- > Paul Bakaus > UI Architect @ smart.fm <http://smart.fm> > -- > http://paulbakaus.com > http://www.linkedin.com/in/paulbakaus > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery UI" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jquery-ui?hl=en -~----------~----~----~----~------~----~------~--~---
