This repository has been archived by the owner on Sep 11, 2024. It is now read-only.
[POC] trust in chrome to do scroll anchoring #1787
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This does not exactly work because it fails when we're at the very top of the page and back paginating. It does however work very very well when paginating whilst the viewport is half-way down the timeline window or whilst at the very bottom. Removing spinners doesn't seem to have any effect. In theory the anchor selection algorithm chrome uses is selecting an element that React decides to turn into a totally new element. There is currently no planned mechanism to prevent some elements from being used as anchors. Chome is also the only browser to support this See https://drafts.csswg.org/css-scroll-anchoring/
|
The decision with this (as it was in Dec '17) is that we're not taking this route until all browsers support scroll anchors and there exists a way to have some elements deliberately jumpy (i.e. the spinners). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This does not exactly work because it fails when we're at the very top of the page and back paginating. It does however work very very well when paginating whilst the viewport is half-way down the timeline window or whilst at the very bottom.
Removing spinners doesn't seem to have any effect.
In theory the anchor selection algorithm chrome uses is selecting an element that React decides to turn into a totally new element. There is currently no planned mechanism to prevent some elements from being used as anchors.
Chome is also the only browser to support this
See https://drafts.csswg.org/css-scroll-anchoring/