- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Sat, 27 Jan 2024 01:50:08 +0000
- To: public-css-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-anchor-position-1] `position-fallback-bounds` vs `position-container` == Afaict `position-fallback-bounds` only affects whether the abspos is considered to overflow for the purposes of triggering fallback positions. I'm having a hard time understanding what use case it might have that wouldn't be covered by a `position-container` that actually changes the containing block (and would have many more use cases besides, see e.g. #9662 and the Apple proposal which approximated this using anchor positioning). Assuming that a fixedpos would continue to check its overflow against the viewport in addition to its containing block, do we really need both of these features? CC @una Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9868 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 27 January 2024 01:50:11 UTC