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

[Master Feature] Doc-level infinite scroll #14059

Open
ericlindley-g opened this Issue Mar 16, 2018 · 3 comments

Comments

@ericlindley-g
Collaborator

ericlindley-g commented Mar 16, 2018

Support document-level infinite scroll, such that when the user reaches the end of the core content of an AMP document (an article, a product detail page, etc), a call can be made to an arbitrary endpoint to fetch additional documents to be dynamically loaded into the view. For the best user experience, users should never see a loading spinner, but instead should either be presented with already-loaded results, or a "recommended content" section to navigate to more.

@ericlindley-g ericlindley-g added this to the Prioritized FRs milestone Mar 16, 2018

@ericlindley-g ericlindley-g self-assigned this Mar 16, 2018

@ericlindley-g ericlindley-g added this to Feature Backlog in AMP HTML Project Roadmap via automation Mar 16, 2018

@ericlindley-g ericlindley-g moved this from Feature Backlog to In Progress in AMP HTML Project Roadmap Mar 16, 2018

@ampprojectbot

This comment has been minimized.

Collaborator

ampprojectbot commented Jun 5, 2018

This issue doesn't have a category which makes it harder for us to keep track of it. @ericlindley-g Please add an appropriate category.

@amedina

This comment has been minimized.

Contributor

amedina commented Sep 29, 2018

Is this capability going to be implemented by removing the limitations of amp-next-page?

@ericlindley-g

This comment has been minimized.

Collaborator

ericlindley-g commented Sep 30, 2018

Yep — the implementation of this feature is amp-next-page. It's available to use as an experiment now, and when we've fixed some bugs that have been identified (analytics in particular, as well as signaling the "active" document so the display & sharing URLs can be updated to match), then the feature will launch to general availability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment