- From: Rune Lillesveen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Dec 2023 12:00:23 +0000
- To: public-css-archive@w3.org
> > Is that really better than authors having to set insets to 0 explicitly? > > Well, without that, you have double-auto inset behavior, which currently implies invoking static positioning (_instead of_ actually positioning relative to the anchor, which you're clearly indicating you want). I thought the double-`auto` inset behavior is what I wanted if I didn't apply any inset properties. I didn't understand how you could possibly get the intrinsic sizing behavior if you forced `auto` insets to 0, but I see now that you can achieve that with `width: fit-content` as that would override the constraints from `left:0; right:0;`. > Are you imagining some additional behavior to make double-auto insets work differently in the presence of inset-area? No. > > and let the anchored element be positioned according to the alignment given by the inset-area spans? > > Note that that's already done in the proposal in item (3), by having inset-area change the behavior of `normal` self-alignment. But it does depend on having a reasonable inset-modified CB set up, which is why the current definition resolves auto insets to 0. -- GitHub Notification of comment by lilles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9598#issuecomment-1840655705 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 5 December 2023 12:00:25 UTC