歴史
- [486] URL Scope to which the manifest applies · Issue #114 · w3c/manifest () https://github.com/w3c/manifest/issues/114
- [269] 27653 – Navigation scope
( 版)
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27653
- [487] define URL Scope (closes #114) (marcoscaceres著, ) https://github.com/w3c/manifest/commit/72d65ad6bdbc52957226f31a6ef3dc27d09a24cd
- [1] Allow for multiple scopes · Issue #449 · w3c/manifest
()
https://github.com/w3c/manifest/issues/449
- [2] Allow for multiple scopes (w3c/manifest #449)
(Rob Dolin著, )
https://lists.w3.org/Archives/Public/public-webappsec/2017Jan/0000.html
[5] Navigation scope: Avoid using pathname field.
(mgiuca著, )
https://github.com/w3c/manifest/commit/c5d899cf9b04e8166ffb1f1a7ea2cb8cf8f5d0ca
[6] Scope matching algorithm: fix and explain by mgiuca · Pull Request #590 · w3c/manifest
()
https://github.com/w3c/manifest/pull/590
[7] Properly define "navigation scope" and "within scope".
(mgiuca著, )
https://github.com/w3c/manifest/commit/1dd908a4653c1c3af0f18ec360bacd996374c449
[8] Properly define "navigation scope" and "within scope".
(mgiuca著, )
https://github.com/w3c/manifest/commit/1dd908a4653c1c3af0f18ec360bacd996374c449
[9] Properly define "navigation scope" and "within scope". by mgiuca · Pull Request #644 · w3c/manifest
()
https://github.com/w3c/manifest/pull/644
[10] "Navigation scope" and "within scope" are poorly defined/used · Issue #643 · w3c/manifest
()
https://github.com/w3c/manifest/issues/643
[11] Navigation scope algorithm takes a URL, not a string.
(mgiuca著, )
https://github.com/w3c/manifest/commit/d2bb750d44350c814e13bb139ea89ee971454d1a
[12] Fix or replace instances of "new URL" by mgiuca · Pull Request #649 · w3c/manifest
()
https://github.com/w3c/manifest/pull/649