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

@mgiuca commented on this pull request.



> +          that will affect all apps installed under that origin. Settings like:
+        </p>
+        <ul>
+          <li>Permissions
+          </li>
+          <li>Storage and storage quota
+          </li>
+          <li>User settings (e.g. font size)
+          </li>
+        </ul>
+        <p>
+          Nested scopes are strongly not recommended. They have the above
+          complications of same-origin scope, along with the following UX and
+          API problems or inconsistencies among other possible consistencies:
+        </p>
+        <ul>

+1 for specifying the behaviour around this (perhaps starting with MAY requirements so we don't require browsers to update right away). It doesn't feel good to say "not work" as a possible outcome.

For simplicity, I'm OK with leaving this here for now, but long-term as you say it would be good for each section to specify "Choose the controlling app".

There's actually prior art for this which we might want to merge into this concept: in the Badging API there's "[determining the set of matching applications](https://w3c.github.io/badging/#determining-the-set-of-matching-applications)" which is a bit weird in that it returns a set but usually only with one item in it. If you just look at the document case (the top half), it's explicitly picking the one with the most specific scope.

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

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