- From: dshin-moz via GitHub <noreply@w3.org>
- Date: Thu, 19 Feb 2026 23:25:28 +0000
- To: public-css-archive@w3.org
FWIW, on Firefox side, we've fixed a few bugs that affects the outcome: [this bug](https://bugzilla.mozilla.org/show_bug.cgi?id=2006352), and [this one](https://bugzilla.mozilla.org/show_bug.cgi?id=2011777). On current Nightly, the demo largely works as expected, I think. Both Chrome and Safari seem to have changed their behaviours as well. Locally, I see that all of them attaches the popover to the anchor, which scrolls with the anchor, and the popover doesn't "stick" to the viewport (I imagine sticking to viewport was unintended - That requires triggering reflows consistently, despite there being no fallback option). As for "where applicable," I think it's abbreviating [the same behaviour](https://drafts.csswg.org/css-anchor-position-1/#position-area) for `position-area`: > The [scrollable containing block](https://drafts.csswg.org/css-position-4/#scrollable-containing-block) is used in place of the [local containing block](https://drafts.csswg.org/css-position-4/#local-containing-block) _when the [absolute-position containing block](https://drafts.csswg.org/css-position-3/#absolute-position-containing-block) is generated by a [scroll container](https://drafts.csswg.org/css-overflow-3/#scroll-container)_, so that the entire [scrollable overflow area](https://drafts.csswg.org/css-overflow-3/#scrollable-overflow-region) (typically) is available for positioning. (Perhaps it should be referencing the paragraph in `position-area` explicitly) -- GitHub Notification of comment by dshin-moz Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13353#issuecomment-3930704883 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 19 February 2026 23:25:29 UTC