- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Apr 2021 17:02:25 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-contain] What is the migration path for Container Queries?`. <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-contain] What is the migration path for Container Queries?<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/6175<br> <dael> miriam: Talked about this last week<br> <dael> miriam: Went to thread.<br> <dael> miriam: Prop to add a container function to supports similar to selector in that you can test a container query property value pair<br> <dael> miriam: Also it would be good to get consistency on how unknown functions or tests are handled<br> <dael> miriam: Other prop is unknown supports conditions evaluate as unsupported<br> <dael> Rossen_: Thank you<br> <dael> Rossen_: With that proposal, are there any other opinions hwere?<br> <dael> TabAtkins: Sounds good<br> <dael> miriam: Prop 1: Any unknown supports conditions should evaluate as unsupported<br> <dael> TabAtkins: Rephrase: unknown support condisions should work the same as unknown media conditions<br> <dael> florian: Clarification, they don't eval to false which is a weird not bool<br> <dael> TabAtkins: Eval to false at top value. Unknown prop as unknown but it doesn't define top level unknown so becomes false<br> <dael> emilio: Do we want @supports NOT [unknown] true or false?<br> <dael> TabAtkins: Same as MQ for unknown things. NOT [unknown] is unknown<br> <dael> miriam: Don't think that works well<br> <dael> emilio: Right. Not great. Can't use @supports NOT container b/c will never match. Returns true for browsers w/o container<br> <dael> miriam: Want it to eval true when negate it<br> <dael> TabAtkins: There's unknown which is syntax we don't understand and syntax that's false b/c you don't impl the thing yet<br> <dael> miriam: To be backwards compat we need unknown to eval true when you negate it so it works with browsers that don't understand container<br> <dael> dbaron[m]: Argument that @supports should be different for MQ. Unknown @supports is like an unsupported feature<br> <dael> Rossen_: We have folks starting to drop off<br> <dbaron[m]> (And I think I was agreeing with miriam.)<br> <dael> Rossen_: Sounds like we want to take this back to the thread, flesh it out, and bring it as first topic this week<br> <dael> TabAtkins: Threat got confused with impl doing weird things. We're past that, just need to discuss on this<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6175#issuecomment-828621618 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 April 2021 17:02:28 UTC