api.Navigator.registerProtocolHandler - status is confusing/misleading
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
What type of issue is this?
Other
What information was incorrect, unhelpful, or incomplete?
A couple of issues with registerProtocolHandler, perhaps already discussed somewhere but I couldn't find an issue here.
Chrome support
Chrome is marked not supporting because of this note:
Given that, it seems odd that Edge is marked as supporting.
Firefox is marked as supporting, but for sure does not load some of the schemes.
Worth poking a bit more.
Mixed support for schemes
The API has a number of keys for schemes underneath it. Support for these schemes may always be mixed.
Does mixed scheme support impact baseline status?
IIRC the approved scheme list is standardized at WHAT-WG. Has there been a determination there that approved schemes are part of the web or not? Given that this a hook for non-browser-native implementations, seems like it'd be hard for that to ever be consistent user experience.
What browsers does this problem apply to, if applicable?
No response
What did you expect to see?
Same support status across Chrome, Edge and Firefox.
Did you test this? If so, how?
Not yet, see notes above.
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
https://github.com/web-platform-dx/web-features/blob/main/features/registerprotocolhandler.yml
https://github.com/web-platform-dx/web-features/blob/main/features/registerprotocolhandler.yml.dist
Do you have anything more you want to share?
No response
MDN URL
No response
MDN metadata
No response
Contributor guide
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 comparing api/Navigator.json with features/registerprotocolhandler.yml and features/registerprotocolhandler.yml.dist, then verify the Chrome, Edge, and Firefox support claims for registerProtocolHandler and its schemes. Done means the compatibility data and baseline status have a documented, evidence-based determination rather than inconsistent or misleading statuses.
Written by the indexing model from the issue text.
Assessment
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100