- From: Simon Fraser via GitHub <noreply@w3.org>
- Date: Thu, 26 Feb 2026 02:19:39 +0000
- To: public-css-archive@w3.org
smfr has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-scroll-anchoring] Does gaining an abspos descendant suppress anchoring? == The [spec](https://drafts.csswg.org/css-scroll-anchoring/#suppression-triggers) says: > Any change to the computed value of the [position](https://drafts.csswg.org/css-position-3/#propdef-position) property on any element within the scrollable element (or document), such that the element becomes or stops being absolutely positioned. This is pretty ambiguous; it doesn't say what happens if an abspos child is added (`appendChild()`) or appears via a change in the `display` property. Firefox treats this as a suppression trigger, Chrome does not. Test at https://codepen.io/smfr/pen/zxKxBWe cc @Emilio I would think that gaining positioned descendants is common enough that having this suppress anchoring on the document would be annoying. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13563 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 February 2026 02:19:39 UTC