- From: fantasai via GitHub <noreply@w3.org>
- Date: Thu, 17 Jul 2025 03:46:18 +0000
- To: public-css-archive@w3.org
@jakearchibald For `anchor-center`: - `unsafe` means center wrt the anchor absolutely, even if it overflows - `safe` means center wrt the anchor unless this overflows the inset-modified containing block (i.e. the area you get when you set `place-content: stretch`), in which case start-align... the goal of the keyword is to make sure there's no clipping (hence "safe") though I guess it's got its own problems (potentially overlapping the anchor). - _neither_ means center wrt the anchor to the extent possible without overflowing the IMCB. If it's too big to fit within the IMCB, then overflow in the direction that keeps the alignment as close as possible to the ideal `anchor-center` alignment; but do not ever overflow the start edge of the containing block. I updated WebKit to match the spec more closely last week and submitted some WPTs for it (though now that I'm reviewing this issue, WebKit might still be slightly off in some overflowing cases). -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12466#issuecomment-3082355028 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 17 July 2025 03:46:19 UTC