📖<amp-next-page> documentation and validation#26841
📖<amp-next-page> documentation and validation#26841wassgha merged 20 commits intoampproject:masterfrom
Conversation
|
Hey @ampproject/wg-caching, these files were changed: |
CrystalOnScript
left a comment
There was a problem hiding this comment.
Please update the md file to follow the format outlined here: https://github.com/ampproject/amphtml/blob/master/build-system/tasks/extension-generator/extension-doc.template.md
Such improves would include updating "Behavior" to "Usage", migrating attributes out of tables, and moving analytics information under the Analytics header.
Please also include any aria attributes and what their behavior does under the Accessibility header, CSS selectors that can be used under the Styling header. A good example is the updated amp-accordion documentation:
https://amp.dev/documentation/components/amp-accordion/?format=websites
Thanks for your help :)
honeybadgerdontcare
left a comment
There was a problem hiding this comment.
Initial review of validation rules done.
Please add comments to your validator test files indicating if an example is valid or invalid and if invalid why.
E.g.
<!-- Valid: Correct use of amp-next-page with next-page-hidden -->
<!-- Invalid: Missing amp-next-page extension -->
CrystalOnScript
left a comment
There was a problem hiding this comment.
GH is getting a little wacky on me - submitting these change requests before they're lost
CrystalOnScript
left a comment
There was a problem hiding this comment.
These comments finish this round of reviews. Thanks :)
| To enable for an infinite loading experience without the need for a server-side configuration (remote-loading), `amp-next-page` automatically enables `deep-parsing` (see Attributes), which allows it to parse more suggestions by recursively looking at inline configurations inside `<amp-next-page>` tags on the loaded documents. To disable this behavior, set `deep-parsing` to `false`. | ||
|
|
There was a problem hiding this comment.
@wassgha I still don't think these questions are answered.
CrystalOnScript
left a comment
There was a problem hiding this comment.
Thanks for the update, its looking a lot better!
I caught some structural changes that were lost. I also have a lot of open questions that are not answered in the document.
extensions/amp-next-page/1.0/test/validator-amp-next-page-remote.out
Outdated
Show resolved
Hide resolved
CrystalOnScript
left a comment
There was a problem hiding this comment.
I added some last minute nits/comments. But overall, looks great - thanks for taking the time to clean it up and clarify!
* master: Launch `amp-next-page` v2 & clean up experiment (ampproject#27035) ✨Implement Display Locking on amp-accordion (ampproject#25867) 📖<amp-next-page> documentation and validation (ampproject#26841) Improve visibility event tests (ampproject#26847) amp-geo: Fall back to API for country (ampproject#26407) ✨ Add customization options to <amp-story-quiz> (ampproject#26714) navigation: Minor test improvements (ampproject#26926) ♻️ Alias video.fullscreen action for symmetry with interface names (ampproject#27017) ✨ Implements `amp-analytics` support for `amp-next-page` (ampproject#26451) ✨ amp-video-iframe integration: global jwplayer() singleton by default (ampproject#26969) Fix unit tests broken by ampproject#26687 (ampproject#27000) Filter redirect info from emails (ampproject#27012) 📖 Make amp-bind doc valid, fix amp-form stories filter (ampproject#27003) url-replacements: Minor test improvement (ampproject#26930) viewport: Minor test improvement (ampproject#26931) amp-consent fullscreen warning (ampproject#26467) dep-check: USE CAPS FOR IMPORTANCE (ampproject#26993) fix img url (ampproject#26987) # Conflicts: # extensions/amp-next-page/amp-next-page.md
Changes
amp-next-pageversion1.00.1rules since there is no way to specify version-dependent validation rules so far).0.1when using features from1.0max-pagesattribute that limits the number of recommendations shown to the user and adds tests for it0.1deep-parsingattribute to allow it to be disabledTo-do
<footer>validation error)next-page-hideandnext-page-replace