Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support more features in AMP.navigateTo()
See original GitHub issueThe AMP.navigateTo() action doesn’t support some navigational features that <a> tags do, e.g. custom protocols and URL replacements. Perhaps it should?
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Developers - Support more features in AMP.navigateTo() -
The AMP.navigateTo() action doesn't support some navigational features that <a> tags do, e.g. custom protocols and URL replacements. Perhaps it should?
Read more >Actions and events - amp.dev
Actions and events ... This documentation covers actions and events for AMP websites, stories and ads. Read Actions and events in AMP email...
Read more >Configure AMP for Endpoints Event Stream Feature - Cisco
Navigate to your AMP for Endpoints portal and login · Under Accounts, choose API Credentials · Click New API Credentials · Enter a...
Read more >AMP-state doesn't work with AMP.navigateTo() - Stack Overflow
Reason behind Uncaught (in promise) Error: Target 'null' not supported. target is not set properly <button on="tap:AMP.
Read more >Uploaded display ads specifications - Google Ads Help
... can upload on the Google Display Network. Learn more about how to upload your own display ads ... You can build ads...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
IIRC, the issue was the inability to support both iOS and Android deep-link URLs in a single anchor. I believe Chris’s workaround was to use amp-access to detect the platform and render the appropriate deep-link at runtime.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.