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

@alancutter commented on this pull request.



> +    </section>
+    <section data-cite="file-system-access">
+      <h2>
+        <dfn>Execute a file handler launch</dfn>
+      </h2>
+      <p>
+        A {{Window/window}} has an associated {{LaunchConsumer}} <dfn>assigned
+        launch consumer</dfn>.
+      </p>
+      <p>
+        A {{Window/window}} has an associated [=list=] of {{LaunchParams}}
+        <dfn>unconsumed launch params</dfn>.
+      </p>
+      <p>
+        When a [=file type=] is registered with a web app and one or more of
+        these registered files are launched on the platform, run the following

I wrote a small [doc](https://docs.google.com/document/d/1EeweceXvS55VLzj-YYgUPIa8sq3vHnYEcy5yvoYX54A/edit) for removing the re-enqueuing on navigation implementation currently in Chrome.

The LaunchQueue/LaunchParams API surface LGTM otherwise.

-- 
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/1005#discussion_r744483986