- From: Matt Giuca <notifications@github.com>
- Date: Mon, 05 Feb 2018 02:35:39 +0000 (UTC)
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 5 February 2018 02:36:02 UTC
FYI, this change has landed and is now live at https://www.w3.org/TR/appmanifest. Implementations should update to the new behaviour. The normative changes are: * If the "scope" member is omitted or invalid, it should now default to the *start URL*, with its filename (final path segment), query, and fragment removed, as specified in [steps for processing the scope member](https://www.w3.org/TR/appmanifest/#dfn-processing-the-scope-member). * There is no longer a concept of "unbounded" scope. Web developers should ensure that either a) the directory that the `start_url` is in encompasses the entire app, or b) they explicitly specify `scope`. This change may restrict the scope of the app compared to what it was previously. However, note that this has been the behaviour of Chrome for Android all along, so likely no change is required. -- 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-362966074
Received on Monday, 5 February 2018 02:36:02 UTC