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

@evanstade 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

> > these steps are also run after every same-origin page navigation
> 
> Can you explain that in a bit more detail? Let's say I launch `//origin1/foo/` using a file, then I click a link in the resulting page to `//origin1/bar/` (creating a same-origin navigation), are you saying the next page gets the file handler too? Or is it just to handle reloads?

The intent is to handle reloads and redirects (the original feature request was for redirects). The implementation works for any same-origin navigation, including link clicking. I believe we could narrow it to just reloads and redirects, although I'm not sure it would capture all possible types of redirects.

-- 
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_r726400898