Re: [w3c/manifest] scope="../" should be invalid (#551)

1) We are defining things inside a manifest which is in one location, so making things relative to that location makes sense (like for any HTML file etc). That is how it is defined today, thus icons and start_url are relative to manifest path.

2) As there is a strong relation between scope and start_url (the latter has to be within scope), it would make sense to divert from the above and let start_url be relative to scope.

3) I think it "makes sense" to have the default scope be "." instead of unbounded. Unbounded seems a bit unsafe and might shock people. On the other hand, if it defaults to "." people will probably start getting their "scope" set :-) Most people use manifest.json in root today so it would make little difference, but this would break sites that are currently not having manifest.json in root, nor having a scope defined.

4) With the above, if "scope" by default is "." that would mean that start_url is also relative to the manifest location, like spec'ed today

-- 
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/issues/551#issuecomment-278302555