- From: gitspeaks via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Nov 2024 17:42:50 +0000
- To: public-css-archive@w3.org
>The alignment within the IMCB is determined by CSS Align as I already said. But it doesn't work in Chrome or Firefox. We already discussed this (align-self: center; and justify-self: center;), so what's the point of bringing it up again? >This means the abspos box can be smaller than the IMCB >Yes. This doesn't require auto insets. Yet another positioning issue remains unaddressed. >No, if the IMCB has a different size than the abspos, you just use CSS Align properties. At most you can affect the resolution of a normal self-alignment. But align properties don’t work. How are we supposed to handle back-compatibility in this case? >CSS2 doesn't handle lots of modern things, like alignment. We are talking about the very essence of positioning in CSS. Do you really think it’s reasonable to redefine the entire semantics of absolute positioning and expect adoption? I’ve read _every point_ in the CSS2 spec you referenced—it’s mathematically precise. The information in the current spec doesn’t even come close to that level of detail. -- GitHub Notification of comment by gitspeaks Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11242#issuecomment-2489202215 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 November 2024 17:42:51 UTC