RESOLVED WORKSFORME 148798
Scroll-Snap together with box-shadow on hover...jumps back to top of window
https://bugs.webkit.org/show_bug.cgi?id=148798
Summary Scroll-Snap together with box-shadow on hover...jumps back to top of window
Lutz
Reported 2015-09-04 06:16:13 PDT
Created attachment 260589 [details] scroll with mouse on red-element shows bug, on green element did not. Use Scroll-Snap together with a extra box-shadow by hover a Scroll-Line-Element, shows a bug. The Bug is, it always jumps/returns to Top of Window, when your scrolling begins with mouse-position on any of that hover-Elements and ends on any of that hover-Elements and mouse move out of that hover-Element (after that it jumps back to Top of Window). In Attachment, see document "testScrollSnap.html". To reproduce the Bug by my attached document, move your mouse-cursor on the first left-side red-hover-element(01), than scroll down with two fingers on your touchpad. After your scroll-down ends, your mouse is still on another red-hover-element, than move your cursor to right with one finger (out of that hover-element). Now you see the bug, it jumps back to Top of Window. This only happens when you scroll on left side red elements. It do not happen when you scroll on right side green elements or any other mouse position outside the red-elements. I only can reproduce the bug when i use a css box-shadow in the hover-effect. Making a hover-effect with the css outline or "cursor: pointer" did NOT had this Bug-Effekt "jump back to top of window".
Attachments
scroll with mouse on red-element shows bug, on green element did not. (9.65 KB, text/html)
2015-09-04 06:16 PDT, Lutz
no flags
Updated test case (8.53 KB, text/html)
2021-07-07 08:41 PDT, Martin Robinson
no flags
Radar WebKit Bug Importer
Comment 1 2015-09-05 14:00:27 PDT
Martin Robinson
Comment 2 2021-07-07 08:41:06 PDT
Created attachment 433033 [details] Updated test case I've updated this test case to snap with the latest css-scroll-snap API. I'm not able to reproduce this issue. Chances are it has been fixed. Thanks for reporting this and please reopen if you can still reproduce it.
Note You need to log in before you can comment on or make changes to this bug.