- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Sep 2023 23:56:50 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-pseudo-4] Support for highlight pseudos declarations inside @container media queries`, and agreed to the following: * `RESOLVED: Disallow the use inside container blocks` <details><summary>The full IRC log of that discussion</summary> <dael> Rossen_: If we need emilio we may have to push<br> <dael> schenney: I think that was around impl complexity<br> <Rossen_> q?<br> <dael> schenney: Question in my mind is do we want to support declaration of new highlight styles inside @container MQs. Different highlight if container has 200px vs 500px? I think not. Then crossed my mind do we want different highlight styles in any MQ?<br> <dael> schenney: Particularly interested in use cases b/c I cna't think of where you would change highlights beyond printing<br> <dael> Rossen_: Even for print I'm struggling to justify that.<br> <fantasai> proposed resolution wfm<br> <dael> schenney: Maybe if your'e scaling font you want underlines to change, but that's covered in font units. Regardless of ease of implementation it requires a use case. I'd propose we do not allow new highlight styles to be defined<br> <dael> Rossen_: Sounds reasonable. Anyone have a use case?<br> <dael> dholbert: You said no MQ or just container?<br> <TabAtkins> I think MQ is too far, that's pretty static and widely applicable.<br> <dael> schenney: I would be happy to exclude from all MQ. If that's too far we can resolve on Container and I'll follow-up with other issue<br> <TabAtkins> I mean, just styling different colors into the highlights based on a MQ is important<br> <dael> dholbert: I can imagine mobile for different highlights. Maybe prefers-contrast as well<br> <dael> dholbert: Seems like there could be a case based on MQ. Restricting for container query seems reasonable<br> <dael> Rossen_: I'd argue for restricting for all and relax the restriction if a use case arises<br> <emeyer> +1 to Rossen_’s point<br> <dael> schenney: Let's resolve on container queries. I can open a new issue on all MQ and I'll take the time to go through them all and think about it more<br> <dael> Rossen_: Yeah. I really wish we could resolve on all MQ. Let's not invent solutions for problems we don't have. There's already enough complexity. Unless there's a strong use case and I didn't hear any<br> <dael> dholbert: I think reduce-contrast may want different colors<br> <dael> TabAtkins: The MQ case to have different colors based on color sceme are removed frrom dynamic styles enough that it doesn't seem reasonable to cut them out. In very rare cases MQ should be disallowed on a CSS Feature<br> <dael> Rossen_: Okay. Prop: Disallow the use inside container blocks. TBD on if further restrictions are needed<br> <dael> schenney: I'll follow up with an issue to confirm on other cases<br> <dael> Rossen_: Obj?<br> <dael> RESOLVED: Disallow the use inside container blocks<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9280#issuecomment-1709271978 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 September 2023 23:56:53 UTC