Re: [w3c/manifest] Make unbounded navigation scope less broad (#550)

A coworker ran a script over the internet's Web Manifests. There are:
~3000 Web Manifests where the start page's directory is more top level than the manifest's directory
~ 50 Web Manifests where the manifest's directory is more top level than the start page's directory

I suggest that if the  Web Manifest does not have a scope, the scope should default to either:
Proposal A: The directory of the start page
OR
Proposal B: The directory of the start page or the directory of the manifest whichever is topmost. If the start page's directory does not contain the manifest's directory and manifest's directory does not contain the start page's directory, the scope is set to the start page's directory

Thus:

Manifest URL | Start URL | Computed Scope Proposal A | Computed Scope Proposal B
-------------------|---------------|----------------------------------------|-------------------------------------------
https://www.nfl.com/manifest/now.json | https://www.nfl.com/now?icampaign=nfl_now_progressiveap | https://www.nfl.com/ | https://www.nfl.com/
https://www.carthage.edu/manifest.json | https://www.carthage.edu/bridge/ | https://www.carthage.edu/bridge/ | https://www.carthage.edu/ (The manifest is more topmost than the start page)
https://m.wikipedia.org/w/api.php?action=webapp-manifest | https://m.wikipedia.org/wiki/Main_Page | https://m.wikipedia.org/wiki/ | https://m.wikipedia.org/wiki/ (https://m.wikipedia.org/w/ does not contain https://m.wikipedia.org/wiki/  and vice versa. Start page directory wins)


-- 
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-279108333