Re: [w3c/manifest] Adding file_handlers and launch consumer (#1005)

@marcoscaceres commented on this pull request.



> +          </li>
+          <li>[=list/For each=] |entry:ordered map| of |json|["file_handlers"]:
+            <ol>
+              <li>Let |file_handler:ordered map| be [=process a file handler
+              item=] with |entry|, |manifest/start_url|, |manifest/scope|, and
+              |manifest_url|.
+              </li>
+              <li>If |file_handler| is failure, continue.
+              </li>
+              <li>[=list/Append=] |file_handler| to |processedFileHandlers|.
+              </li>
+            </ol>
+          </li>
+        </ol>
+        <p>
+          On [=installation=], a user agent SHOULD run the process to

> Can you clarify how you suggest the text here should change?

If we wanted to get fancy, we could have throw these into some kind of "steps to run on installation" which would have a queue of actions to run. The intent here is clear enough for now though.   

>  The user agent might not register these associations with the OS at installation time, but pop up a toast when the app is later launched to confirm the user wants the associations.

Right, I see...

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/1005#discussion_r832988513
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/pull/1005/review/918381627@github.com>

Received on Wednesday, 23 March 2022 08:34:00 UTC