foolip

The CSS Working Group has resolved to relax the syntax in https://github.com/w3c/csswg-drafts/issues/7961 so what you desire is coming :)

I'm one of the people working on https://github.com/web-platform-dx/feature-set. Only 4 features are only marked as Baseline currently, for a minimal initial launch on MDN. The ambition is to cover the whole web platform, and at that point a list of all Baseline features could be generated.

Fixed now, thanks for spotting and reporting!

(I'm quite sure the demo was built using Firefox, but then the screenshot was taken later.)

You're right! Unfortunately, a single test to cover lots of important details makes it much harder to understand what works and what doesn't.

Most tests are pretty boring nowadays, green squares like this: http://wpt.live/css/css-sizing/aspect-ratio/replaced-element...

I guess Subgrid tests are a bit more interesting to look at: http://wpt.live/css/css-grid/subgrid/subgrid-mbp-overflow-00...

The Acid tests still live on in WPT though, if you want to smile: http://wpt.live/acid/acid2/reftest.html http://wpt.live/acid/acid3/test.html

If you scroll to the bottom of https://wpt.fyi/interop-2022 you can see how these scores are calculated.

Interop 2022 organizer here, working on Google Chrome.

By and large, prioritization was driven by web developer signals. Results from State of CSS 2021 [1] were quite influential, but we also referred back to the 2020 MDN Browser Compatibility Report [2] and the 2021 Scroll Survey Report. [3]

https://github.com/web-platform-tests/interop-2022/issues/4 is a good example of how the sausage was made.

I think Subgrid, Viewport Units and Scrolling are clear cases of features that web developers want or struggle with, and which I'm very happy are included in Interop 2022.

This doesn't tell the whole story, though. The Web Compat focus area and "Editing, contenteditable, and execCommand" + "Pointer and Mouse Events " investigation efforts are rather motivated by site compat issues that affect users.

An issue like https://github.com/webcompat/web-bugs/issues/25070 is certainly very important to Firefox users, but it's not clear if it could be fixed by aligning browsers on some specific set of tests. My understanding is that Mozilla did look over their top site compat issues and included bugs that seemed tractable within Interop 2022, and some of those are in https://github.com/web-platform-tests/interop-2022/labels/co....

[1] https://2021.stateofcss.com/en-US/opinions/#browser_interope... [2] https://insights.developer.mozilla.org/reports/mdn-browser-c... [3] https://web.dev/2021-scroll-survey-report/

We use Azure Pipelines for https://github.com/web-platform-tests/wpt with some help from friends at Microsoft, and it's a great product!

It's very "power user" in that it's easy to get lost amongst all the options, but nothing else I've tried has the same breadth of OSes and ability to have one job depend on another in intricate ways. And, 10 free parallel builds, including macOS!

The creation of a tag can presumably trigger actions.

It doesn't matter, but couldn't help but notice that the honorable form feed (U+000C) was missing from the definition given. https://infra.spec.whatwg.org/#ascii-whitespace is the concept used in the HTML parser. (https://html.spec.whatwg.org/multipage/parsing.html)

I know it's not quite what you're asking for, but each commit gets its own URL that you can use if you want to refer to a bit of text and know the link won't break: https://html.spec.whatwg.org/commit-snapshots/0184feb8b468f2...

Typo fixed, thanks!