- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Sat, 09 Sep 2023 18:47:41 +0000
- To: public-css-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-anchor-1] Area-specific styling == There are a number of things an author might want to change depending on which fallback position an anchor-positioned element lands in. Accommodating tethers is just one example, e.g. you might want a background gradient drawing outward from the anchor or other effects. We might not want this right away, but we probably want it eventually, so we should design a system that can easily accommodate it. The current proposal uses a limited set of properties inside the `@try` blocks. In theory this list could be expanded. But * the more styling we allow, the more awkward this becomes, since the author can't organize their styles in more sophisticated ways * the more styling we allow, the worse the [cascade problem](https://github.com/w3c/csswg-drafts/issues/9331) becomes Note: It's not totally worked out in Apple's proposal, but the fact that each fallback position can be identified and selected against lays out a path for extending styling as far as we want to go in the future. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9332 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 9 September 2023 18:47:44 UTC