web-platform-tests / web-platform-tests/interop
Reconsider the browser specific failures graph
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 524
- Forks
- 35
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
The WPT Core Team decided last year to defer RFC 122 to the Interop Team, and there was an expectation this would be dealt with after Interop 2023 launched. Thus it's now worthwhile looking at this; I'd suggest sticking to comments in the RFC repo rather than here, but adding this here partly as an Agenda+ item.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading RFC 122 in the RFC repository and the discussion about its deferral to the Interop Team after Interop 2023 launched. The work is done when the browser-specific failures graph has an agreed direction, with the decision and any resulting changes documented through the RFC discussion.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100