- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Nov 2021 18:11:09 +0000
- To: public-css-archive@w3.org
Agenda+ to see if we can get a resolution on this. I think it's the final blocker keeping browsers from shipping this feature. The more I look at it, the more convinced I am about taking the simple approach here: with a named `initial` layer that can be ordered like any other layer. We always want to give the final site author control over the final layer order, and any attempt to have layers declare their own position relative to the default goes against that goal. Frameworks should not be able to place themselves above or below the initial layer. The final author should make that decision by establishing layer order up front. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6323#issuecomment-964406534 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 November 2021 18:11:11 UTC