ampproject / ampproject/amphtml
amp-next-page can't work with amp-bind
- Dominant language
- JavaScript
- Stars
- 14.9k
- Forks
- 4.1k
- PR merge metrics
- No merged PRs in 30d
Description
### Description
amp-next-page can cause amp-bind feature can't work when you put them together.
### Reproduction Steps
We can use the amp project offical example to test the bug.
step1: Open the amp-bind example page on official site. We will test the bug on the page.
https://playground.amp.dev/?url=https%3A%2F%2Fpreview.amp.dev%2Fdocumentation%2Fexamples%2Fcomponents%2Famp-bind
step2: Open and copy the relative amp-next-page codes to step1 page. Now we put amp-next-page and amp-bind component together.
https://playground.amp.dev/?url=https%3A%2F%2Fpreview.amp.dev%2Fdocumentation%2Fexamples%2Fcomponents%2Famp-next-page&_gl=1*1qbi6a4*_ga*YW1wLV9ReGVPMWt3OVYwWS1ZN3g4aGk0a2c.
step3: Scroll down to make sure amp-next-page works. Then you scroll back to top, click the amp-bind feature button. You will find the button can't work.
### Relevant Logs
```shell
no error log report.
```
### Browser(s) Affected
all
### OS(s) Affected
all
### Device(s) Affected
all
### AMP Version Affected
_No response_
Contributor guide
Research direction
Reproduce the issue using the linked amp-bind and amp-next-page Playground examples, then inspect the amp-next-page and amp-bind component entry points. Confirm whether loading the next page disables the existing amp-bind button, and use continued button functionality after scrolling as the completion check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100