- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Nov 2023 18:33:14 +0000
- To: public-css-archive@w3.org
That's conceptually like the up/down proposal earlier in the thread, just a different syntax for it. Which then morphed into the slash-syntax that we brought up for debate. It means we're tracking two distinct layer orders (the top one and the bottom one). That was rejected last time we discussed, with concerns for the complexity of nested layers, and interactions between layers from different parts of a large style system. Which is what I've been trying to get at here. How much combinatorial complexity and arms-race-for-importance are we willing to accept? To move a proposal forward here, we have to not only show a syntax that could work to solve these use-cases, but also show that it doesn't cause a lot of potential new issues. Can we do this and avoid the complexities of z-index, or the arms race of importance? Have we considered what happens when third-party tools do this internally, and then we import those tools? -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6323#issuecomment-1804348137 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 November 2023 18:33:16 UTC