Issue metadata
Sign in to add a comment
|
Removing element causes parent scroll up the height of the element removed.
Reported by
joolscha...@gmail.com,
Feb 15 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. Navigate to https://jsfiddle.net/JoolsCaesar/b4e990va/ 2. Scroll down until you can see "3" 3. Click "Remove page 1" What is the expected behavior? The scroll tab should not move. You should find you're self looking at "4" because the content has moved up. What went wrong? The scrollable element scrolls up, the height of the element removed. Did this work before? N/A Chrome version: 56.0.2924.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0 This does not occur on any other browser.
,
Feb 16 2017
,
Feb 16 2017
,
Feb 17 2017
Issue similar to the bug 692608 .Hence merging this into 692608. Please feel free to undupe if not similar Thanks,
,
Feb 17 2017
The cause is likely the same, though I'd say that bug 692608 is a subcase of this one. The problem probably isn't anything to do with position:sticky (given this bug doesn't use it), but rather the fact that editing the content of a scrollable div in a number of ways is shifting the scroll positions when it shouldn't. My latest jsfiddle shows that you can do this in a number of ways, including just increasing the height of content above the current view. https://jsfiddle.net/JoolsCaesar/b4e990va/7/
,
Feb 20 2017
I've just taken a closer look at the examples in bug 692608 and I can't see how the bugs are even similar, never duplicates. His is describing "position:sticky" elements become unstuck, so they can be scrolled out of view. What this bug describes, is chrome actually scrolling content when the content changes and has nothing to do with "position:sticky" elements. How do I undupe this?
,
Feb 21 2017
Unduped as per comment #5 & 6.
,
Feb 21 2017
,
Feb 23 2017
Able to reproduce the issue on Windows 10, Mac 10.12.2 and Ubuntu 14.04 using chrome reported version #56.0.2924.87 and latest canary #58.0.3020.0. Bisect Information: ===================== Good build: 55.0.2860.0 Revision(418438) Bad Build : 55.0.2861.0 Revision(418732) Change Log URL: https://chromium.googlesource.com/chromium/src/+log/02a4849687aa7a52e3af8959484f7f8b6b9335cf..73693c4b2eb516e55b700c0317b38d672a0bdb29 From the above change log suspecting below change Review url: https://codereview.chromium.org/2335363003 skobes@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Thanks...!!
,
Feb 23 2017
This is the intended behavior of the scroll anchoring feature, which launched in Chrome 56. For more information about scroll anchoring, see the explainer at: https://github.com/WICG/ScrollAnchoring/blob/master/explainer.md |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by joolscha...@gmail.com
, Feb 15 2017