[webkit-dev] What to do about scroll anchoring?
simon.fraser at apple.com
Sat Sep 28 03:08:37 PDT 2019
> On Sep 27, 2019, at 10:08 PM, Emilio Cobos Álvarez <emilio at mozilla.com> wrote:
> And, to be clear, we _can_ fix these compat issues, some way or another.
> One thought is to limit the amount of scroll adjustments without user scrolling or stuff like that, which would prevent the "you get stuck on the page".
> Making anchoring opt-in rather than opt-out is another option, but that defeats most of the purpose of the feature, I guess.
> See also some of the Chromium docs on the compat issues they found and how were they trying to fix them before adding the "layout-affecting-property changed" heuristic, which is what is on the spec right now and what they implement.
> I just think that these are very hacky heuristics that are just going to bring a lot of compat pain and developer confusion.
> It doesn't help that all these things can break or not depending on the speed at which the user scrolls, the amount of scroll events that the user dispatches, the timing of these events relative to other events, etc…
I expressed my main issue with scroll anchoring at the F2F, which is that it’s an on-by-default behavior that is making up for bad web authoring, and is harmful if only implemented by a subset of browsers.
I would support removing it entirely, or having it be opt-in.
More information about the webkit-dev