- From: Diego Gonzalez <notifications@github.com>
- Date: Mon, 28 Jun 2021 02:51:17 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/manifest/pull/972/review/693766423@github.com>
@diekus commented on this pull request. > + </p> + <p> + How protocol handlers are presented, and how many of them are shown + to the user, is at the discretion of the user agent and/or operating + system. + </p> + <p>To <dfn>process the `protocol_handlers` member</dfn>, given [=object=] |json:JSON|, |manifest:ordered map|, and |manifest URL:URL|:</p> + <ol> + <li>Let <var>processedProtocolHandlers</var> be a new [=list=]. + </li> + <li>[=list/For each=] <var>protocol_handler</var> (<a>protocol handler description</a>): + <ol> + <li>If |protocol_handler|["protocol"] or + <var>protocol_handler</var>["url"] is undefined, [=iteration/continue=]. + </li> + <li>Let (<dfn>normalizedProtocol</dfn>, <dfn>normalizedUrl</dfn>) be the result of running <a data-cite="HTML/system-state#normalize-protocol-handler-parameters">normalize protocol handler parameters</a> with <var>protocol_handler</var>["protocol"], <var>protocol_handler</var>["url"] using <var>manifest URL</var> as the base URL, and [=this=]'s relevant [=environment settings object=]. If the result is failure, [=iteration/continue=].</li> I've gotten the [=normalize protocol handler parameters=] definition exported in HTML. 👍🏼 -- 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_r659643097
Received on Monday, 28 June 2021 09:51:29 UTC