- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Nov 2024 16:05:47 +0000
- To: public-css-archive@w3.org
> it doesn't explain why the #child div aligns to the top-right edge of the inset-modified containing block Mm, yeah. So I think we have to options: - Keep saying that a lone `auto` inset resolves to zero. But then we need a `normal` self-alignment to resolve to either `start` or `end`, whichever side has the non-auto inset. - Stop saying that a lone `auto` inset resolves to zero. Instead, resolve the `auto` inset to whatever value makes the size of the inset-modified containing block match the fit-content size of the abspos. This fit-content size shrinks-to-fit into the original containing block size minus the non-auto inset, or equivalently, into a tentative inset-modified containing block with the `auto` offset resolved to 0. The difference is observable when setting the self-alignment to e.g. `center`. All browsers seem to be doing the 2nd option. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11242#issuecomment-2486131051 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 November 2024 16:05:48 UTC