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

mgiuca commented on this pull request.



> +      <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 a copy of <var>shortcut.url</var>.
+          </li>
+          <li>Let <var>header list</var> be a new empty <a data-xref-for=
+          "request">header list</a>.
+          </li>
+          <li>If <var>shortcut.params</var> <a data-cite="infra/#list-contain">

Oh OK, I didn't know there was consideration to support POST. Now that you mention it, why was it decided not to? Is it "maybe in the future" or we have an active reason not to?

I agree it would be a little weird to click a shortcut and have it perform some side effect, and it's probably a better user experience to take you to a GET page that asks if you want to perform the side effect first. So I'm cool with disallowing POST but just wanted to get the rationale.

-- 
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#discussion_r324494913