- From: Marcos Cáceres <notifications@github.com>
- Date: Mon, 24 May 2021 20:11:31 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 25 May 2021 03:11:44 UTC
@marcoscaceres commented on this pull request.
> + <p>
+ In the following example, the developer has included two
+ <a>protocol handler description</a> <var>protocol_handler</var>s. Assuming
+ the the manifest's URL is
+ <samp>https://example.com/manifest.webmanifest</samp>:
+ </p>
+ <ul>
+ <li>The first protocol handler would register to handle "web+music"
+ URLs (e.g.: web+music://#1234). When activated, the user agent
+ would instantiate a new <a>top-level browsing context</a> and
+ navigate to
+ <samp>https://example.com/play?songId=web+music://%231234</samp>.
+ </li>
+ <li>The second protocol handler would be ignored, as the protocol
+ provided does not start with "web+" and is not part of the
+ safelist.
```suggestion
[=safelist=].
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/972#pullrequestreview-667352860
Received on Tuesday, 25 May 2021 03:11:44 UTC