Re: [csswg-drafts] [mediaqueries-5] Parsing strategy for range syntax (#8998)

The CSS Working Group just discussed `[mediaqueries-5] Parsing strategy for range syntax`, and agreed to the following:

* `RESOLVED: restrict comparison syntax to the mf-numeric-value production, not the mf-value production`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael_> TabAtkins: It was pointed out that the mathematical syntax for MQs, specifically equals, &lt;, >, etc didn't restrict the value very well. You could say resolution = infinite. You need to know too much information to know what's the MQ, what's the keyword<br>
&lt;dael_> TabAtkins: I think it's an oversite<br>
&lt;dael_> TabAtkins: prop is when you use comparision syntax we restrict value to numbers, dimensions, ratios. If you want a keyword you use colon syntax<br>
&lt;dael_> astearns: Opinions?<br>
&lt;dael_> TabAtkins: I think this is just an oversite. It's a mature spec so we need a resolution<br>
&lt;dael_> astearns: Prop?<br>
&lt;fantasai> makes sense to me<br>
&lt;dael_> TabAtkins: Restrict compare syntax to the mf-value production<br>
&lt;dael_> astearns: Objections?<br>
&lt;dael_> Restrict compare syntax to the mf-numeric production<br>
&lt;TabAtkins> restrict comparison syntax to the mf-numeric-value production, not the mf-value production<br>
&lt;dael_> RESOLVED: restrict comparison syntax to the mf-numeric-value production, not the mf-value production<br>
</details>


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


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

Received on Wednesday, 2 August 2023 23:54:44 UTC