-
Notifications
You must be signed in to change notification settings - Fork 19
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
manifest must be embedded in primary entry page #333
Comments
Yes. Absolutely! |
And semi-related... how does a WP-aware RS/AU know that a non-primary-entry-page resource is part of a WP. E.g., a link to "chapter 27" -- how does such a RS/UA know to jump into "WP mode" following that link? And, yea, all the "part of multiple WPs" issues arise too. |
If we want any SEO value from the contents of the manifest, it MUST be embedded in the entry page. |
This is closed with #335. |
As discussed in PR #331, there are currently no restrictions on what resource can contain the embedded manifest. Proposal is to restrict to the primary entry page (must provide a link to the manifest or must embed the manifest).
The text was updated successfully, but these errors were encountered: