Re: [csswg-drafts] [css-contain-3] Should style() queries allow !important flag? (#7413)

The CSS Working Group just discussed `[css-contain-3] Should style() queries allow !important flag?`.

<details><summary>The full IRC log of that discussion</summary>
&lt;astearns> topic: [css-contain-3] Should style() queries allow !important flag?<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/7413<br>
&lt;argyle> astearns: who's gonna take this one?<br>
&lt;argyle> florian: the syntax for style container queries, lets you specify a property declaration representing the computed value, and grammar wise, a prop dec can include !important. but that has no effect on th computed value<br>
&lt;argyle> florian: q is, shouuld we ban writing !Important or should be keep it even tho it has no effect?<br>
&lt;astearns> ack fantasai<br>
&lt;emilio> q+<br>
&lt;argyle> fantasai: i think we should disallow this becaues it represents a computed value, it has no concept of where it exists in the cascade<br>
&lt;florian> q+<br>
&lt;argyle> fantasai: i dont feel the same about @supports rules which have a siimilar sytnax, in that case, you're asking is this syntax supported and then it's fine to have !important be part of that. but if add another !something later, it'd return null<br>
&lt;astearns> ack emilio<br>
&lt;argyle> emilio: i think i disagree with fantasai because even tho it does rep the computed value, what you write is a specified value. you can query color: blue, and it's computed then compared, but<br>
&lt;argyle> emilio: it's a specified value right<br>
&lt;astearns> ack florian<br>
&lt;miriam> q+<br>
&lt;argyle> florian: i dont feel strongly, seems to me it's easier if we can copy/paste declarations from where they define and test them, to test. that might drag a !impportant along the way. if we allow it in @supports, could support it here as well. but i dont feel strongly<br>
&lt;astearns> agrees with the copy-paste argument<br>
&lt;astearns> ack miriam<br>
&lt;argyle> miriam: was thinking about resolving variables, custom properties in a query, but they won bring along !important. never mind, i'm fine either way<br>
&lt;argyle> florian: if you're using actual css var, your'e right, but if you're using server side processor that has something similar to variables, it might<br>
&lt;argyle> miriam: that's true<br>
&lt;argyle> astearns: we are out of time, is anyone else convinced byt he copy paste arg to not make a change to the sepc?<br>
&lt;argyle> astearns: or should we continue discussion int he issue?<br>
&lt;argyle> astearns: not going to get reslution to this, we will continue in the issue. bring it back to the agenda onde we have clarity<br>
&lt;masonf> Thank you Adam!<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7413#issuecomment-1225994302 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 24 August 2022 17:01:19 UTC