- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Mon, 13 May 2024 01:20:14 +0000
- To: public-css-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-anchor-position] should alignment safety consider the containing block? == Alignment has a concept of "safety", which is, we try to bias alignment in a direction that won't result in clipping the content. For `unsafe` centering, we don't care; but for `safe` centering we overflow away from the unscrollable region. For anchor positioning (and absolute positioning in general to be fair), there's two containers that are of interest: the inset-modified containing block, and the actual containing block. Should the default behavior and/or the `safe` behavior of an overflowing alignment bias towards staying within the containing block if possible, before finally overflowing the end/end edges? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10316 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 13 May 2024 01:20:14 UTC