web-platform-tests / web-platform-tests/interop
Retitle some Focus Areas to stop confusion
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 524
- Forks
- 35
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
Currently several of the Focus Area names listed on the dashboard are confusing people.
For example, it's easy to get the impression that neither Safari nor Firefox have any support for IndexDB, when both browsers shipped it long ago. I've seen similar confusion about CSS attr().
Also, it's inconsistent how some CSS API are prefixed "CSS" and others are not. Plus, it's not called "JS Navigation API" or "HTML Dialogs". I'm not sure how CSS became necessary to call out as something different.
Here's a list of proposed changes:
- CSS anchor positioning —> Anchor Positioning
- CSS attr() —> Advanced attr() since
attr()is already supported in browsers, and this is about adding advanced capabilities - CSS contrast-color() —> contrast-color()
- CSS shape() —> shape()
- Dialogs and popovers —> Dialog & popover additions
- IndexedDB —> getAllRecords() for IndexedDB
Maybe the CSS functions that need to be lowercase since its code could continue to be prefixed with CSS. But to be consistent with Media pseudo-classes, Scroll-driven animations, Scroll snap and more, Anchor Positioning can drop the "CSS". Same with Advanced attr().
Changing the names to Advanced attr(), Dialog & popover additions, and getAllRecords() for IndexedDB make it clear what these are — and what's not included.
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 at the dashboard's Focus Area list and compare each displayed name with the six proposed replacements in the issue. Update the names consistently, then verify that the dashboard shows the revised wording and that the names make each scope clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- content
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100