- From: Aaron Gustafson <notifications@github.com>
- Date: Mon, 27 Sep 2021 16:03:33 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 27 September 2021 23:03:45 UTC
> In this situation, it's not clear where this pathing will be resolved. This behavior is outlined in [the spec](https://www.w3.org/TR/appmanifest/): > Let image be the result of running process an image resource from JSON given potential image and manifest URL The reason is that the manifest can be linked to from anywhere in a domain (not just a single page). I believe we've discussed `base_url` in the past, but it has not become a part of the spec. In light of that, I suggest you use absolute URLs for your assets (e.g., /sub/assets/image.png) or move your manifest to the /sub folder (rather than /sub/foo/) to resolve the issue you're experiencing per the spec. -- 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#issuecomment-928409561
Received on Monday, 27 September 2021 23:03:45 UTC