- From: fantasai via GitHub <noreply@w3.org>
- Date: Mon, 06 Oct 2025 21:59:32 +0000
- To: public-css-archive@w3.org
Agenda+ to re-raise @bfgeek's compat concerns in https://github.com/w3c/csswg-drafts/issues/10258#issuecomment-3207602473
In particular, when trying to implement this in WebKit, I found multiple WPT tests were failing because they had set `margin: 0` expecting this to disable the centering behavior, and it seems likely we'll see similar patterns in the wild.
I don't love the idea of disabling `auto` margins in conjunction with `position-area` but it might be the only reasonable option we have given the situation. Here are some options we have:
* If `position-area` is not `none`, disable `auto` margins (unconditionally).
* If `position-area` is not `none` or `center` in an axis, disable `auto` margins.
* The default alignment in the center track is centering anyway...
* If `position-area` is not `none`, `center`, or `span-all` in an axis, disable `auto` margins.
* These symmetric cases are the ones where the author is most likely to want to use `auto` margins. If we take this option, we also need to make `anchor-center` disable `auto` margins.
* Do one of the above, but only if alignment is `dialog`.
I think the best option here is the third one, possibly conditioned on `dialog`. I think authors will be confused if they place items into the center track and `auto` margins don't work as they expect.
Also open to other ideas...
--
GitHub Notification of comment by fantasai
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10258#issuecomment-3374397145 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 6 October 2025 21:59:33 UTC