- From: Phil Kunz via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Mar 2022 23:53:28 +0000
- To: public-css-archive@w3.org
@tabatkins Sounds pretty wrong to me. - You want to break with the logic of css variables (which is the most confusing thing you can do here) - You want to complicate the API of Custom Components by limiting their ability to act as containers for their light dom children. A custom element should be in control of its light dom children. Thats true for css variables, and it is EXACTLY the same thing for CQs. By limiting the childrens ability to see CQs in a slotted context, you move into global space for handling such things, causing collisions in the aftermath. **Its as wrong as not having scoped element registries from the start, or not enabling font-face in shadow dom... same rubbish.** What are container queries even good for, if I end up at the browser window after all, when not wanting to manually rewire containers for every slot? -- GitHub Notification of comment by philkunz Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5984#issuecomment-1059611130 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 March 2022 23:53:30 UTC