Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"Navigation scope" and "within scope" are poorly defined/used #643

Closed
mgiuca opened this issue Jan 29, 2018 · 0 comments
Closed

"Navigation scope" and "within scope" are poorly defined/used #643

mgiuca opened this issue Jan 29, 2018 · 0 comments

Comments

@mgiuca
Copy link
Collaborator

mgiuca commented Jan 29, 2018

In the "Navigation scope" section:

  • It never defines how you get a navigation scope from a manifest. (Obviously, you look at its "scope" member after post-processing, but it doesn't say that.)
  • Lots of references to "navigation scope" just say "the navigation scope", rather than "the navigation scope of ".
  • Some references to "within scope" just say "if within scope", rather than saying "within scope of ."

So a quick clean-up is needed to formally specify "navigation scope" and "within scope" and always use them appropriately.
mgiuca added a commit to mgiuca/manifest that referenced this issue Jan 29, 2018
@mgiuca
Properly define "navigation scope" and "within scope".
88992a6 
Previously, the spec did not explicitly say that you get the navigation
scope of a manifest by looking at its "scope" member. Now it does. Also:

- All references to "navigation scope" are given a specific manifest, and
- All references to "within scope" are given a specific scope URL.

Closes w3c#643.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mgiuca