Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Map interop focus areas to web-feature IDs #928

Open
captainbrosset opened this issue Feb 17, 2025 · 1 comment · May be fixed by #930
Open

Map interop focus areas to web-feature IDs #928

captainbrosset opened this issue Feb 17, 2025 · 1 comment · May be fixed by #930

Comments

@captainbrosset
Copy link
Contributor

The web-features project is a catalog of the entire web platform, from the point of view of web developers. The project contains a list of (almost) all of the features of the platform, and provides (either directly or indirectly) links from this data to a bunch of other web platform-related data, such as compat, specs, documentation, surveys, vendor positions, etc.

Learn more about web-features.

I'd love for the interop focus areas to be linked to web-features IDs. The focus areas that got selected in interop-2025 are almost all covered by web-features already, here are a few:

backdrop-filter - backdrop-filter
Core Web Vitals - largest-contentful-paint, missing INP feature
CSS anchor positioning - anchor-positioning
<details> element - details
Layout - grid, subgrid, flexbox
Modules - json-modules
Navigation API - navigation
Pointer and Mouse events - pointer-events-api
Remove mutation events - mutation-events
@scope - scope
scrollend event - scrollend
Storage Access API - storage-access
text-decoration - text-decoration
URLPattern - urlpattern
View Transitions - view-transitions, view-transition-class

Creating a mapping between the two projects would be beneficial:

  • This could allow linking from Interop dashboard to MDN directly.
  • This could help raise awareness about Interop and the current focus areas via the multiple places which display web-features data already.

I don't think this has to be very fancy. A json file inside the 2025 folder could work, and I'm willing to contribute it via a PR if people agree.

Note that there's also a way to link WPT tests to web-features already. For example, the feature:grid filter returns all of the tests that relate to the grid web-features entry. But this is slightly different than this. This mapping is for focus areas, not tests, and aims to bring visibility to Interop, not only WPT.

@foolip
Copy link
Member

foolip commented Feb 20, 2025

As you'd expect given my web-features affiliation, I like this idea a lot. I'd be happy to fix any weirdness we find in web-features along the way.

There won't be a 1:1 correspondence between focus areas and features, and in particular there may be more tests for a feature than are included in a focus area. So I think the relationship is "this focus area covers parts of features X, Y, and Z."

@captainbrosset captainbrosset linked a pull request Feb 20, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants