Hmm... I was under the assumption that one could know on a mousemove event whether the mouse button is pressed and then add a mousemove listener to window and properly know if we're still dragging the element or not... But my current experimentations aren't discovering any way to know this. As far as you know, could this perhaps be possible?
-- http://thewe.net On Sun, Feb 14, 2010 at 6:08 PM, Aaron Newton <[email protected]> wrote: > That commit is a test for drag.move's offset computation because IE6 has > offset compute problems inside iframes. This has nothing to do with moving > the mouse out of the iframe (or, for that matter, out of the window). The > issue here is if you move the mouse out of the window, there are no more > events fired for the mouse; no mouse move, no mouse click, etc. The solution > we have in place is to "drop" the object on click. So if it's still stuck to > the mouse, most people have the instinct to click again. If you have another > idea on how to fix this, I'd love to hear it. > > > On Thu, Feb 11, 2010 at 10:25 PM, Avital Oliver <[email protected]> wrote: > >> Friends, >> >> When one uses Sortables inside an iframe and an element gets dragged out >> of the iframe its in and then the mouse is let go weird stuff happens (when >> you go back into the inframe it thinks the mouse is still clicked). This >> seems like it shouldn't be hard to fix and I'm willing to go on and do it, >> but I think maybe someone is working on it because I found this: >> http://github.com/appden/mootools-more/commit/f90d72b6bfed9ccedf32526490adfba91d757b36, >> even though I found nothing similar in Lighthouse. >> >> What is the status of this bug? >> >> Avital. >> >> -- >> http://thewe.net >> > >
