Re: [w3c/manifest] Add shortcuts feature to the explainer and spec (#768)

christianliebel commented on this pull request.



> +          representations of the shortcut in various contexts.
+        </p>
+      </section>
+      <section>
+        <h3>
+          <dfn>Launching a shortcut</dfn>
+        </h3>
+        <p>
+          When <a>ShortcutItem</a> <var>shortcut</var> having
+          <a>WebAppManifest</a> <var>manifest</var> is invoked, run the
+          following steps:
+        </p>
+        <ol>
+          <li>Let <var>url</var> be <var>shortcut.url</var>.
+          </li>
+          <li>Let <var>browsing context</var> be the result of creating a new

What does "new top-level browsing context" mean here? Would it create a new window in all cases? On desktop platforms, it would rather be common to reuse one of the existing windows (or launch the app with given parameters when it’s closed).

I think these steps are okay if the application isn't open. During runtime, I'd suggest raising an `onshortcutclick` event on a service worker which can then override the default behavior (e.g. by navigating an existing client window or opening a new one).

-- 
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/768#pullrequestreview-289014651