Proposal to map focus areas to web-features #930
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@foolip I've added you as a contributor to my fork of this repo so you can push commits to my PR branch. |
foolip
reviewed
Feb 21, 2025
| @@ -0,0 +1,21 @@ | |||
| { | |||
| "interop-2025-backdrop-filter": ["backdrop-filter"], | |||
| "interop-2025-core-web-vitals": ["largest-contentful-paint"], | |||
There was a problem hiding this comment.
We need to add INP to web-features.
| @@ -0,0 +1,21 @@ | |||
| { | |||
| "interop-2025-backdrop-filter": ["backdrop-filter"], | |||
There was a problem hiding this comment.
Yep, looks like the same identifiers as here:
https://github.com/web-platform-tests/wpt.fyi/blob/e418d972cd3a352af13aabdf7b7ebe989580d5a5/webapp/static/interop-data.json#L1387-L1405
| "interop-2025-textdecoration": ["text-decoration"], | ||
| "interop-2025-urlpattern": ["urlpattern"], | ||
| "interop-2025-view-transitions": ["view-transitions", "view-transition-class"], | ||
| "interop-2025-webassembly": [], |
There was a problem hiding this comment.
There are lots of wasm features in web-features, don't any of them match?
There was a problem hiding this comment.
Probably some of them do, I just haven't done the research yet.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #928.
This is a proposal to map Interop focus areas to web-features IDs.
This is just the start of the PR. @foolip offered to help with the mapping.
Ideally, there could be such a file in each of the folders of the repo.
I've chosen to use wpt tags as keys in the JSON object because:
But:
interop-2023-eventshas been reused), which would make it harder for a consumer of this data to know which iteration of interop to link to.One option would be to add another level of nesting to the JSON object like
{ "year": 2025, "focus-areas": {...} }.Or move the file to be at the root level and structure it like:
{"2022": {...}, "2023": {...}, "2024": {...}, "2025": {...}}.