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

Adding protocolhandlers #969

Closed
wants to merge 3 commits into from
Closed

Adding protocolhandlers #969

wants to merge 3 commits into from

Conversation

diekus
Copy link
Member

@diekus diekus commented Apr 12, 2021

Closes #863

This change (choose at least one, delete ones that don't apply):

  • Breaks existing normative behavior (please add label "breaking")
  • Adds new normative recommendations or optional items
  • Makes only editorial changes (only changes informative sections, or changes normative sections without changing behavior)
  • Is a "chore" (metadata, formatting, fixing warnings, etc).

Implementation commitment (delete if not making normative changes):

If change is normative, and it adds or changes a member:

Commit message:

Adds "protocol_handlers" member to the manifest spec, referencing the process that navigator.registerProtocolHandler uses.

contributors:
+@fabiorocha

Person merging, please make sure that commits are squashed with one of the following as a commit message prefix:

  • chore:
  • editorial:
  • BREAKING CHANGE:
  • And use none if it's a normative change

Preview | Diff

fabiorocha and others added 3 commits May 4, 2020 14:20
Adds a reference to the step in the algorithm that defines the registration of protocol handlers in the HTML spec.
Ran the doc through tidy html and added a couple of references to the scheme and url members of the registerProtocolHandler method.
Copy link
Member

@marcoscaceres marcoscaceres left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for taking first stab at this @diekus.

Few things: we've dropped IDL from the spec, so be good to update to match the updated style. Similarly, we don't have "issue a developer warning" anymore.

There also need to be some strong security assurances around those URL replacements. It might be worth looking at how Web Share Target handles that (or perhaps some other specs that do something similar).

<li>Let <var>url</var> be <var>protocol_handler.url</var>.
</li>
<li>Replace the first occurrence of the exact literal string "%s" in
<var>url</var> with an escaped version of the absolute URL.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The "an escaped version" needs some definition (or link to) of how to do the escaping.

@diekus
Copy link
Member Author

diekus commented Apr 14, 2021

I'm closing this PR since I've noticed how far behind it is and it's simpler to branch from the current state of main for now and apply the new changes there..

@diekus diekus closed this Apr 14, 2021
@diekus diekus mentioned this pull request Apr 26, 2021
4 tasks
@w3c w3c deleted a comment Dec 1, 2021
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

Successfully merging this pull request may close these issues.

3 participants