Re: [csswg-drafts] [mediaqueries][css-conditional] Allow empty functions in <general-enclosed> (#6803)

The CSS Working Group just discussed `Allow empty functions in <general-enclosed>`, and agreed to the following:

* `RESOLVED: Accept change to allow empty functional notations in <general-enclosed>`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: Allow empty functions in &lt;general-enclosed><br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/6803<br>
&lt;fantasai> TabAtkins: We had some leftover grammar from a previous change that accidentally implied that if you had a &lt;general-enclosed> in functional form it had to ahve something inside the parens<br>
&lt;fantasai> TabAtkins: previously could be empty<br>
&lt;fantasai> TabAtkins: small change to make the value optional, so that foo() would be valid<br>
&lt;TabAtkins> @media fn() {...}<br>
&lt;TabAtkins> @media fn(foo) {...}<br>
&lt;fantasai> TabAtkins: wanted to make sure this counts as &lt;general-enclosed> with unknown value rather than syntax error<br>
&lt;fantasai> florian: asking for approval because spec is in CR<br>
&lt;fantasai> RESOLVED: Accept change to allow empty functional notations in &lt;general-enclosed><br>
</details>


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


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

Received on Wednesday, 15 December 2021 17:35:36 UTC