Philip Jägenstedt

These are good questions. The important part to avoid sudden breakage of CI is that the IDs are pinned in some way. An NPM package makes that easy and allows...

Good point about not all IDs being good feature links, I didn't even consider other linkable things like examples and whatnot. I strongly suspect that doing this will reveal lots...

https://github.com/mdn/browser-compat-data/pull/23129 shows the changes that the collector can make after this fix.

@queengooborg done!

@marcoscaceres looking at the test results here, it looks like 3 tests have gone missing: https://wpt.fyi/results/clipboard-apis?diff&filter=ADC&run_id=5200303578677248&run_id=4800456115617792 The same can be seen for Chrome and Firefox. Can you check what might...

Thinking about where documentation for this would be discoverable, at minimum it should show up in https://web-platform-tests.org/search.html?q=web_features. It doesn't fit cleanly in any existing section in https://web-platform-tests.org/#table-of-contents, but under "Writing...

> The date the feature became available (if applicable) for each browser This information isn't in web-features, but could be derived from web-features and BCD together. If the use cases...

See also https://github.com/GoogleChrome/webstatus.dev/issues/280 about JSON. We probably only need one format, or at least 99% of the implementation should be the same regardless of format.

Regarding Test262, I made an attempt in https://github.com/web-platform-dx/web-features/pull/1054 but found that most likely we'll also need to identify some features by path. Then we would also need results from stable...

See also https://github.com/GoogleChrome/webstatus.dev/issues/305 about CSV. We probably only need one format, or at least 99% of the implementation should be the same regardless of format.