URL Protocol Handler Registration for PWAs

[samtan-msft]

Hello TAG!

I'm requesting a TAG review of URL Protocol Handler Registration for PWAs

This feature will allow web developers to register web applications as URL protocol handlers via a property in the web app manifest. The apps would open directly when a custom-scheme URL is visited. Implementation-wise, we intend to build this feature by reusing registerProtocolHandler internally and modifying the protocol handler registry and shell integration classes to account for the existence of PWAs. The idea is to avoid code duplication and maintain the APIs aligned. (see explainer and design doc for more details)

• Explainer: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/URLProtocolHandler/explainer.md
• Security and Privacy self-review: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/URLProtocolHandler/SecuritySelfReview.md
• Primary contacts:
  • Diego Gonzalez @diekus, Microsoft
  • Fabio Rocha, @fabiorocha, Microsoft
  • Jason McConnel, @Maggers, Microsoft
  • Connor Moody, @connor-moody, Microsoft
  • Samuel Tang, @samtan-msft, Microsoft
• Organization/project driving the design: Microsoft
• External status/issue trackers for this feature: https://chromestatus.com/features/5151703944921088

Further details:

• I have reviewed the TAG's API Design Principles
• The group where the incubation/design work on this is being done (or is intended to be done in the future): WICG
• Existing major pieces of multi-stakeholder review or discussion of this design:
  w3c/manifest#846
  blink-dev
  WICG discourse thread
• Major unresolved issues with or opposition to this design: None
• This work is being funded by: Microsoft

We'd prefer the TAG provide feedback as:

💬 leave review feedback as a comment in this issue and @-notify @fabiorocha @Maggers @connor-moody @samtan-msft

[torgo]

@samtan-msft thanks for sending this. Do you have an idea where this might go after incubation in WICG?

[fabiorocha]

@torgo we initially thought about having it incubated in WICG, but as discussed on this thread the spec side of this work might be rather small and it has been suggested it could be treated as a spec bug and discussed as an issue on the manifest repo. What do you think?

@marcoscaceres how does that sound to you? We already have w3c/manifest#846, and we could just iterate there?

[samtan-msft]

Hey, quick question, is anyone looking at this on the TAG side at this moment?