Re: [csswg-drafts] [css-contain] `scroll-state(stuck)` CQs can easily cause flickering that is very hard to work around (#13898) from Lea Verou via GitHub on 2026-05-12 (public-css-archive@w3.org from May 2026)

From: Lea Verou via GitHub <noreply@w3.org>
Date: Tue, 12 May 2026 20:51:27 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-4434697684-1778619085-noreply@w3.org>

`scroll-anchor: none` on `section` seems to work too, and scopes it a little better: https://codepen.io/leaverou/pen/JobKgJQ
Are there any downsides to it? I'm not very familiar with `scroll-anchor` either.
Is this a workaround to evangelize to authors or something we can bake in to the spec? Are there any use cases where we *want* scroll anchoring? What if `scroll-state` containment automatically disabled scroll anchoring? (though in the case of stuck containers, the container is the element being stuck, and disabling scroll anchoring on it does nothing…)

-- 
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13898#issuecomment-4434697684 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 12 May 2026 20:51:31 UTC