Re: [w3c/manifest] Add scope conflict section about same-origin and nested scopes (PR #1034)

@aarongustafson requested changes on this pull request.



> @@ -2434,6 +2434,59 @@ <h3>
           </p>
         </aside>
       </section>
+      <section class="informative">
+        <h3>
+          Web Apps with scope conflicts
+        </h3>
+        <p>
+          It is possible for two web apps to be installed where there are
+          conflicts between the scope. These conflicts come with disadvantages
+          outlined below and they are generally not recommended.
+        </p>
+        <ul>
+          <li>The scopes of the two web apps can be on the same origin. Not

Do you think the "Not recommended" (and similar) bits should be _emphasized_?

> +        <h3>
+          Web Apps with scope conflicts
+        </h3>
+        <p>
+          It is possible for two web apps to be installed where there are
+          conflicts between the scope. These conflicts come with disadvantages
+          outlined below and they are generally not recommended.
+        </p>
+        <ul>
+          <li>The scopes of the two web apps can be on the same origin. Not
+          recommended.
+          </li>
+          <li>The scope of one web app can be nested inside the scope of the
+          other. Strongly not recommended.
+          </li>
+          <li>The scopes of the two web apps can be the same. Strongly not

The other two have expansions below. Should this one be bundled with nested scoping in that expansion?

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

Message ID: <w3c/manifest/pull/1034/review/971515354@github.com>