You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
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.
The text was updated successfully, but these errors were encountered:
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."
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-filterCore Web Vitals - largest-contentful-paint, missing INP feature
CSS anchor positioning - anchor-positioning
<details>
element - detailsLayout - grid, subgrid, flexbox
Modules - json-modules
Navigation API - navigation
Pointer and Mouse events - pointer-events-api
Remove mutation events - mutation-events
@scope
- scopescrollend
event - scrollendStorage Access API - storage-access
text-decoration
- text-decorationURLPattern - urlpattern
View Transitions - view-transitions, view-transition-class
Creating a mapping between the two projects would be beneficial:
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.
The text was updated successfully, but these errors were encountered: