I find the proposed solution really difficult to read and process. Indeed, what @Loirooriol suggests would address a lot of these use cases, but not all. I wonder if a better solution would be some way to reference the `&` of ancestor scopes (maybe `&1`, `&2` etc?) -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6330#issuecomment-851592637 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Monday, 31 May 2021 16:42:55 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 2 July 2022 03:21:44 UTC