[w3c/manifest] Specify how to handle Relative Paths (#1009)

Hello,

I recently ran into an issue with relative pathing. It seems that the manifest relative paths resolve using the manifest's path, rather than the current webpage that referenced the manifest.

For example, 

**Webpage**: /sub/foo.html

**Manifest**: /sub/foo/manifest.json (assets/image.png)


In this situation, it's not clear where this pathing will be resolved.

Chrome will try to get the image from /sub/foo/assets/image.png.

I think it an option/field to specify how these relative paths should be handled might be useful for some people.

-- 
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/1009