- From: pkotwicz <notifications@github.com>
- Date: Mon, 06 Feb 2017 09:08:18 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 6 February 2017 17:08:58 UTC
>From https://crbug.com/688889 When a user adds a page which contains a Web Manifest to the homescreen in Chrome all of the pages within the Web Manifests' scope get special treatment. It is currently valid for a web manifest in http://rootsweb.ancestry.com/~peter/manifest.json to have scope="../" In my opinion this is suboptimal because this would apply the special treatment specified by http://rootsweb.ancestry.com/~peter/manifest.json to all of http://rootsweb.ancestry.com/ http://rootsweb.ancestry.com/ is a web hosting service which grants each user hosting within a different subdirectory within http://rootsweb.ancestry.com/ There does not seem to be many web hosting services which grant users a sub directory but they seem to still exist http://www.free-webhosts.com/free-web-hosts.php I suggest requiring a Web Manifest scope to be within the directory which contains the Web Manifest Examples: Manifest URL https://www.example.com/subdir/manifest.json Scope '.' Valid Scope 'deeper_subdir' Valid Scope '../' Invalid Scope '../other_subdir' Invalid Scope 'deeper_subdir/../../other_subdir' Invalid -- 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/551
Received on Monday, 6 February 2017 17:08:58 UTC