- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Mar 2023 12:19:46 +0000
- To: public-css-archive@w3.org
kizu has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-anchor-1] `anchor()` inside an `inset` shorthand == <details> <summary>Disclaimer and additional links</summary> I'm submitting my feedback following my experiments with the current implementation of anchor positioning in Chrome Canary. I wrote an article about my experiments, but decided to fill most of my feedback as separate issues here. A quick summary of related links: - [anchor positioning specs](https://drafts.csswg.org/css-anchor-position-1/) - [my article with the experiments](https://kizu.dev/anchor-positioning-experiments/) </details> In my experiments I often did the following: ```CSS top: anchor(--my-anchor top); right: anchor(--my-anchor right); bottom: anchor(--my-anchor bottom); left: anchor(--my-anchor left); ``` What I would want to be able to do instead: ```CSS inset: anchor(--my-anchor); ``` Currently, this does not work, and the specs do not define how the anchors inside the `inset` should behave. Because the current Chrome Canary implementation does not seem to support `auto` and `auto-same`, I'm unable to check if those would help, but maybe they will? I did not really dig into the fallback stuff yet, so not entirely sure if any of those would solve this use case. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8582 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 March 2023 12:19:48 UTC