- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 Dec 2023 19:04:30 +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). Are you imagining some additional behavior to make double-auto insets work differently in the presence of inset-area? > 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 tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9598#issuecomment-1839287901 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 4 December 2023 19:04:32 UTC