[csswg-drafts] [mediaqueries] Prose for `scan` media-feature is misleading (#12226)

AtkinsSJ has just created a new issue for https://github.com/w3c/csswg-drafts:

== [mediaqueries] Prose for `scan` media-feature is misleading ==
The text [here](https://drafts.csswg.org/mediaqueries/#scan) makes a couple of claims that seem to be wrong: (bold mine)

> progressive
>    A screen using “progressive” rendering displays each screen fully, and needs no special treatment.
>    Most modern screens, and **all computer screens, use progressive rendering.**

And:

> Note: At the time of writing, **all known implementations match scan: progressive** rather than scan: interlace.

These suggest that `(scan: progressive)` should match in the general case.

However, the [results for this WPT test](https://wpt.fyi/results/css/mediaqueries/test_media_queries.html?label=master&label=experimental&aligned) show that all 4 major browsers agree that `@media (scan)`, `@media (scan: progressive)` and `@media (scan: interlace)` do not match.

I assume the text is just outdated, and was true when this section of the spec was originally written. Perhaps a more useful note would be something like:

> Note: Most modern displays are not scanning, and so will not match any value for `scan`.

As a side note, it seems odd to me for a test to make assertions about the device. Getting a worse WPT score because you're using an old CRT or some other unusual hardware setup doesn't seem desirable.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12226 using your GitHub account


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

Received on Friday, 23 May 2025 10:06:22 UTC