- From: Diego Gonzalez <notifications@github.com>
- Date: Mon, 24 May 2021 06:15:30 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/manifest/pull/972/review/666724265@github.com>
@diekus commented on this pull request. > + represents a protocol that the web application wants to handle. It has + the following members: + </p> + <ul> + <li>[=`protocol`=] + </li> + <li>[=`url`=] + </li> + </ul> + <p> + A user agent SHOULD use these values to register the web application as + a handler with the operating system. When the user activates a protocol + handler URL, the user agent SHOULD run <a>Handling a protocol + launch</a>. + </p> + <p class="note"> The process itself is the same. This is the way to handle the protocol launch from the manifest instead of from the `registerProtocolHandler()` API. Furthermore, following this link explains that the "_same steps used to invoke a protocol handler defined in HTML_" are the ones that apply. These steps are the ones defined in [the `.registerProtocolHandler()` method steps](https://html.spec.whatwg.org/multipage/system-state.html#protocol-handler-invocation). Since this is another entry point to the steps and that it is stated that they are the same ones defined in the HTML spec, I don't think it impacts the mentioned API nor that it is relevant here. -- 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#discussion_r637935958
Received on Monday, 24 May 2021 13:15:43 UTC