Re: [csswg-drafts] [css-2025][mediaqueries-5] Add Media Queries 5 to Rough Interop (#12712)

The CSS Working Group just discussed `[css-2025][mediaqueries-5] Add Media Queries 5 to Rough Interop`, and agreed to the following:

* `RESOLVED: close, no change`

<details><summary>The full IRC log of that discussion</summary>
&lt;astearns> ack ChrisL<br>
&lt;Zakim> ChrisL, you wanted to wonder who the real editors of MQ5 are<br>
&lt;emeyer> ChrisL: We have a long list of editors and not sure how many are real<br>
&lt;TabAtkins> yeah that's just me and florian, then<br>
&lt;emeyer> florian: I’m no longer funded to work on this, so I’m real but not active<br>
&lt;emeyer> SebastianZ: test coverage is at 81%; a lot of open issues, with about 50 substantial to the spec level; 10 within the spec<br>
&lt;emeyer> …some WPTs are still missing, but the important ones are there<br>
&lt;ChrisL> q+ to say inline &lt;wpt> would be super helpful here<br>
&lt;emeyer> …not all features are supported by all browsers, but the main ones are<br>
&lt;florian> q+<br>
&lt;emeyer> …it could be the whole spec goes to Rough Interop, or we could break things down by feature<br>
&lt;astearns> ack ChrisL<br>
&lt;Zakim> ChrisL, you wanted to say inline &lt;wpt> would be super helpful here<br>
&lt;TabAtkins> Agree, I think this would both benefit from inline wpt, and be appropriate for cherry-picking<br>
&lt;emeyer> ChrisL: THis is a case where because the spec doesn’t have inline WPT annotations, it’s hard to know what’s tested/implemented and which not<br>
&lt;emeyer> …I suspect there are some that are very widely supported, and some not<br>
&lt;emeyer> florian: I agree, and also some features are very hard to test<br>
&lt;emeyer> …All browsers are able to parse the thing and respond, but you can’t always tell if they do the right thing<br>
&lt;emeyer> …We probably need to do a slow walk through here to figure out which things are supported and which are nto<br>
&lt;emeyer> s/nto/not/<br>
&lt;emeyer> …Stuff like environment blending probably not well supported<br>
&lt;emeyer> SebastianZ: Sounds like I should take these back and propose specific features to go to the safe section<br>
&lt;emeyer> florian: Agreed<br>
&lt;emeyer> …Want to also ask what we do about media-queries-4<br>
&lt;emeyer> …I don’t know if we have figured out how to test if the right behavior is happening<br>
&lt;emeyer> …We haven’t really done anything with this in a long time and that’s not good<br>
&lt;emeyer> …I don’t think the tests are good enough<br>
&lt;emeyer> SebastianZ: The next section for level 4?<br>
&lt;emeyer> florian: I think it’s probably ready, but we haven’t checked if browsers are doing what they should<br>
&lt;emeyer> ChrisL: This is work later in the year, not for the snapshot<br>
&lt;emeyer> astearns: Luke Warlow is listed as an editor for level 5<br>
&lt;emeyer> …Maybe Luke could work on tests for level 5, or have ideas on how they could be tested<br>
&lt;emeyer> florian: We have to think it through as a group<br>
&lt;emeyer> astearns: Do we leave open, or close no change?<br>
&lt;emeyer> florian: I think close no change, with an action on SebastianZ to triage issues<br>
&lt;emeyer> SebastianZ: Agreed<br>
&lt;emeyer> RESOLVED: close, no change<br>
</details>


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


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

Received on Wednesday, 3 September 2025 15:42:28 UTC