- From: pkotwicz <notifications@github.com>
- Date: Mon, 06 Feb 2017 08:54:36 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 6 February 2017 16:55:12 UTC
kenchris: For the sake of clarity: Chrome currently uses the manifest URL as the base URL if the scope URL is specified. Thus if the Web Manifest specifies: start_url="https://www.example.com/subdir/deeper/even_deeper/index.html" manifest_url="https://www.example.com/subdir/manifest.json" scope="deeper" The resolved scope is "https://www.example.com/subdir/deeper/" I think that you are suggesting that if the Web Manifest specifies: start_url="https://www.example.com/subdir/deeper/even_deeper/index.html" manifest_url="https://www.example.com/subdir/manifest.json" (no scope is specified) The resolved scope should be "https://www.example.com/subdir/" instead of "https://www.example.com/subdir/deeper/even_deeper/" which is what Chrome currently computes -- 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/550#issuecomment-277742424
Received on Monday, 6 February 2017 16:55:12 UTC