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.

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

primary entry page must be added to reading order when reading order not specified #334

Closed
mattgarrish opened this issue Sep 12, 2018 · 3 comments

Comments

@mattgarrish
Copy link
Member

As discussed in PR #331, the default reading order is required, but the primary entry page may be omitted from it when it is the only resource it would contain. Missing is a statement that, in this case, user agents must add the primary entry page to the default reading order when compiling the infoset.

@mattgarrish mattgarrish changed the title primary entry must be added to reading order when reading order not specified primary entry page must be added to reading order when reading order not specified Sep 12, 2018
@HadrienGardeur
Copy link

Isn't that covered in step 6 of the canonical manifest algorithm?

@mattgarrish
Copy link
Member Author

Yes, but there should be a clearer statement in 4.4.1.1 that matches the expected behaviour. All it says right now is that the entry page can be omitted.

@mattgarrish
Copy link
Member Author

This is closed with #335.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants