Issue metadata
Sign in to add a comment
|
Calling preventDefault on scroll event no longer prevents horizontal scrolling from triggering back/forward actions
Reported by
marcello...@gmail.com,
Apr 14 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. Open the following link in a new tab http://itemslide.github.io/ 2. Navigating back/forward should not be possible in this tab because it's new so the navigation history is empty 3. Try to use trackpad horizontal scrolling to scroll the horizontal div with cards - it should work! 4. Open the same link (http://itemslide.github.io/) from an existing page 5. The back button should now be enabled (it should be possible to navigate back in the tab's history) 6. Try to use trackpad horizontal scrolling to scroll the same horizontal div back and forward - it will no longer work! Scrolling back will send 1 scroll event to the div, and all the following events will go straight to the "back action animation" (the black semi-circle with an arrow that indicates a back action will be triggered once the scroll gesture is released) What is the expected behavior? Calling preventDefault on scroll events should prevents horizontal scrolling from triggering back/forward actions, this is an important feature as it allows developers to use horizontal scrolling in horizontal timelines, carrousels, etc. What went wrong? This behavior suddenly stopped working, and now there seems to be no way to capture horizontal scrolling in an element without triggering navigation actions if they are available - i.e.: if there are pages to navigate back/forward to Did this work before? Yes Probably 64 Chrome version: 65.0.3325.181 Channel: stable OS Version: OS X 10.12.6 Flash Version: This bug significantly impacts usability on my web-based educational video editor: https://www.liberaakademio.com/
,
Apr 14 2018
Update: restarting my browser fixed the problem (no updates took place during the restart). So I'm not sure how this bug got triggered in the first place. I think this issue can be closed.
,
Apr 15 2018
,
Apr 16 2018
As per comment#2 by reporter it is understood that the issue has been resolved, hence closing the issue and marking it as Won't fix. Thanks! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 Deleted