- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Mon, 22 Dec 2025 23:06:13 +0000
- To: public-css-archive@w3.org
The issue with pretending that the existing `position: fixed` is actually one of our new special values is that it has weird behavior when it gets caught by a fixpos containing block that's a scroller; for legacy reasons, we *must* treat it as using the local CB of the scroller. In general, tho, we want the new good behavior to be to consistently use the fixed CB whether you've reached the root scroller or get caught by a lower scroller. As we say in the OP: > For compat reasons, position-container: farthest; position-attachment: fixed may need to convert to local attachment if intercepted by a CB before the root (but it would be nice if we could not do this). So this me not doing that. ^_^ `position:fixed` retains that weird legacy behavior, but `position: absolute farthest scrollport;` doesn't. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12607#issuecomment-3684481110 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 22 December 2025 23:06:14 UTC