- From: Xiaocheng Hu via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Nov 2022 22:54:41 +0000
- To: public-css-archive@w3.org
Discussed with @bfgeek offline:
- We still want to involve the inset-modified containing block rect (or some variation of it) for position fallback, because overlapping with anchor in some trivial cases is bad
- The inset-modified rect (or variation) should not involve scroll offsets. We don't see how it can ever work otherwise
- We still need more work on this idea to support cases like the one I gave in the last comment
One idea is to somehow (conceptually) turn the fallback positions into, e.g.
```
@try { left: anchor(--a left); right: calc(anchor(--a left) + 100vw); }
```
In other words, if one side of the inset-modified rect has anchor queries and the other side is `auto`, then we adjust the other side to fit in the OOF.
--
GitHub Notification of comment by xiaochengh
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8059#issuecomment-1332839231 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 November 2022 22:54:43 UTC