- From: Jonathan Watt via GitHub <sysbot+gh@w3.org>
- Date: Sun, 20 Oct 2024 22:52:01 +0000
- To: public-css-archive@w3.org
Yeah, I get it. They're named with a resulting **effect** in mind given suitable values for **other** properties. But these keywords set a single edge to a length that matches a particular position, the position being another edge. That edge itself is not "inside" or "outside" anything. The other keywords for `<anchor-side>` are clearly positions, but these keywords are not, which I still think will end up confusing some other people too. To me, something like `inset: anchor(near-edge);` seems as good as `inset: anchor(inside);`, and `left: anchor(far-edge)` seems as good as `left: anchor(outside)`. (shrug) Regarding your current examples working well, that relies on authors not thinking there's an inference that the names involve side effects to get a particular effect, ending up trying things like `left: anchor(outside); right: anchor(right);` (result in zero width). -- GitHub Notification of comment by jwatt Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11052#issuecomment-2425271778 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 20 October 2024 22:52:02 UTC