Re: [w3c/manifest] Change the default value for start_url (#670)

@boyofgreen:
> In our case, if there is no start URL, we do assume the top level "/" of the site to which the manifest is served from. I think that is aligned unless I'm missing something.

Sorry, but that's not what we're proposing here. This proposal makes the default start URL the directory containing the manifest. So if a site has its manifest URL at `https://example.com/myapp/manifest.json` with a missing `start_url` member:

- The current proposal makes it so that the start URL is `https://example.com/myapp/`.
- It sounds like Edge currently sets the start URL to `https://example.com/`.

So we aren't aligned. Do you think you could change Edge behaviour to pick the directory containing the manifest in the future? Or should we change the proposal here?

Note that there was a discussion about "." vs "/" above. I gave some arguments for why we prefer "." in [this comment](https://github.com/w3c/manifest/pull/670#issuecomment-391186524), summarized as "URLs on the Web are always relative by default", so I would prefer ".", but if we have to change to "/" for compat with Edge, we can do so. Please let me know what you'd like to do.

-- 
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/670#issuecomment-403683480