Re: [w3ctag/spec-reviews] Review request for Scroll Anchoring (#142)

Thanks @triblondon, I have fixed the typo in 2.1 and added a link to the explainer.

The suppression triggers are mainly to handle pages that implement various forms of "sticky headers".  In the simplest case, script simply toggles position:fixed on a header element below a scroll offset, causing the content to shift by pulling it out of flow.  We've also seen animation on document body padding at the transition.  See e.g. http://crbug.com/601906 and http://crbug.com/641814.

I think the reuse of overflow-anchor makes sense because scroll anchoring and sticky scrollbars are two alternative strategies for connecting scroll position to layout.  It wouldn't make sense to want both at the same time.

The infinite-scroller content loop is an interesting idea, we haven't encountered scenarios like this in practice.  Typically a scroll-triggered content load inserts at the bottom and not the top.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/142#issuecomment-257652134