Closed artlantis closed 10 years ago
Thanks so much for filing the bug. I will look at this on Monday and let you know what I find. Cheers, GS
Oh yeah, this is a big fat bug alright...
@artlantis Thanks for finding this!
--------BUG NOTES------ to reproduce: In FF v31, open test.js, let tests complete and then attempt to click and drag the stream to a new location. Note: experiment with not releasing the pointer right away.
expected results: the stream moves in synch with scroll axis observing all easing rules. (see any webkit browser -- it works there)
actual results: When pointer is clicked and in a 'mouseDown' state, the stream does not move as the pointer is moved. A subsequent mouseUp event causes tremulajs to 'see' subsequent pointer move events normally -- however, at this point -- tremulajs acts as if we are still in a mouseDown state. So that's bad.
Note to self: There were some recent event rule changes with the recent native scroll-axis events enhancement. Could this be a regression? I will look there first.
Also, would be nice to create some tests around this kind of interaction.
Tried to roll back native scroll-axis events. This did not fix the issue. So, this must be an old bug. Still needs work.
FIXED. With reservation.
So, In FF the IMG element is trapping events in an unexpected way. when IMG is display:none the problem goes away. adding pointer-events:none; does fix the issue -- although I don't understand really why behavior is different. Will be pushing to GH soon.
Ok. It's pushed out. Would be great if anyone following wants to verify. Cheers!
works well, thank you Garris.
I tried both IE and Chrome which is working well. But, in Firefox v31, there is a bug. When we slide the items, the mouse hang up an image which we should click again to leave.