- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Sun, 19 Mar 2023 12:59:20 +0000
- To: public-css-archive@w3.org
kizu has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-anchor-1][css-pseudo] Should we allow anchoring things to more pseudo-elements? == - [anchor positioning spec](https://drafts.csswg.org/css-anchor-position-1/) - [pseudo-elements spec](https://drafts.csswg.org/css-pseudo/) Did a few more experiments just to see what is available: https://codepen.io/kizu/pen/MWqBRPw There I tried to use `anchor-name` on pseudo-elements like `::first-letter`, `::first-line` and `::marker`. It doesn't work for any of those, probably with the main reason in `anchor-name` not being present in the list of allowed styles (it works for `::placeholder` though, which can be fun). However! Given that the anchored elements do not impact their target — should we allow this? Potential use-cases: ability to add various decorations to those pseudo-elements that are not available for them otherwise — like interesting borders, complex backgrounds, and so on. Using anchored elements for this seems like it could be a nice workaround. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8615 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 19 March 2023 12:59:22 UTC