Philip Jägenstedt

We discussed this in https://github.com/web-platform-tests/interop/issues/660. Concrete next steps here could be a GitHub Actions workflow that does: - Get list of labels for active focus areas from https://wpt.fyi/static/interop-data.json - Get...

How about documenting this in a README in https://github.com/web-platform-tests/results-analysis/tree/main/interop-scoring and linking it from https://wpt.fyi/interop-2023? For keeping historical results unchanged, an alternative way to achieve that is to move labels into...

I agree this isn't great, and it also causes a bit of inflation in general for multi-global tests on wpt.fyi. There I've often thought that we should use the manifest...

I'm not aware of any hurdles we'll run into fetching and using the manifest from JS. The main issue is that it would be very slow. Storing all manifests in...

This came up again in https://github.com/web-platform-tests/interop/issues/281. We have cases (URL) where we want to include some variants but not others, so that rules out a "clean" approach of labeling file...

Summary from the notes: > When we have variants, we can group them using information from the manifest, score them individually, and divide by the number of variants in the...

We've discussed this in a meeting. We have a pretty good idea of what we'd change to address this, but nobody assigned to do the work.

I have sent https://github.com/web-platform-tests/interop/pull/667. Editorial review is the main thing that's needed.

We issued a call for change requests in https://github.com/web-platform-tests/interop/issues/524 and discussed in https://github.com/web-platform-tests/interop/issues/599. Quick/easy changes can probably still be done, but for anything substantial we need to make sure there's...

I've filed these issues after discussion in #619: - https://github.com/web-platform-tests/wpt.fyi/issues/3639 - https://github.com/web-platform-tests/wpt.fyi/issues/3640