Re: [w3c/manifest] Shortcut_items uses manifest_url when it should use start_url (#1003)

I worry that doing relative to scope might cause breakage here as previous relative urls are relative to the manifest url. This means that existing sites that have the manifest url at, say, `site.com/site_a/resources/manifest.json`, and then their scope is `site.com/site_a`, could have have relative urls like so: `start_url: "../../index.html"`, which resolves w/ the manifest base url as `site.com/site_a/index.html`.

If we changed the base_url to be the scope, then this would make it resolve to `site.com/index.html`.

This has come up a LOT as confusion for folks, and obviously for webapps. I think that we either:
1. Decide to possibly break sites by changing the base_url of everything to start_url or scope, or
2. Make it more obvious in the specification that relative urls are resolved in terms of the manifest_url, and to avoid confusion absolute urls should be used.

Obviously 1. would break things so I don't think we should do that.

I bet that #1018 could include the documentation.

-- 
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/1003#issuecomment-962054407