Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Protocol handlers should not normatively handle the protocol launch (HTML already does this) #64

Open
mgiuca opened this issue Nov 7, 2022 · 0 comments

Comments

@mgiuca
Copy link
Member

mgiuca commented Nov 7, 2022

There's a section here "Handling a protocol launch" which says:

When a protocol handler description protocol_handler having manifest manifest is invoked, it goes through the same steps used to invoke a protocol handler defined in HTML, where the user agent SHOULD navigate to url and the appropriate browsing context is set to a new top level browsing context.

However, if I'm right, I believe this is redundant and doesn't need normative text at all.

In "Processing the protocol_handlers member", there is a step:

For each processedProtocolHandlers, the user agent SHOULD register a protocol handler.

This means that we are explicitly invoking the HTML registration system, which would set up the scheme and URL found in the manifest within the user agent handler database. Therefore, HTML will automatically invoke the protocol handler when a navigation is detected to that protocol. There is no need to have any normative text under "Handling a protocol launch".

That section could be replaced with a non-normative note, explaining that this is so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant