Closed dreamofabear closed 6 years ago
Just confirming, does per-link opt in only include anchor links or is it for all navigation features?
Does this have the same behavior on and off caches?
Nice!
@lswang1618 All navigation features eventually, <a>
first.
@ithinkihaveacat Good question. Off cache this is a no-op.
This is a high priority issue but it hasn't been updated in awhile. @choumx Do you have any updates?
Feedback from design review https://github.com/ampproject/amphtml/issues/12939#issuecomment-362006871:
<a rel="amphtml">
instead of new boolean attribute?For links:
<a rel=amphtml href="amp.html">An AMP link</a>
For forms and actions:
<!-- Per-feature opt-in based on `content` attribute. -->
<meta name="amp-to-amp-navigation" content="AMP-Redirect-To; AMP.navigateTo">
<a rel="amphtml noamphtml">
<meta>
tag instead of boolean attributerel
attribute: http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions/cc @cramforce
Looks good as discussed in review. No semiconolon in content
.
FYI: I've put together an extension that implements A2A linking for sites using the AMP plugin, when that feature is implemented by an AMP viewer. See more at https://github.com/ampproject/amp-wp/issues/1389#issuecomment-459126087.
Features for publishers to specify navigation from an AMP page to another AMP page when served from CDN:
<a href="example.com/amp" amp>
AMP.navigateTo
,AMP-Redirect-To
) with new boolean attribute on HTML tag e.g.<html a2a-by-default>
Notes:
a2a
capability and page -> viewer message. SeenavigateTo()
in viewer-impl.jsamp-href
to normal<a>
URLs that it already has a cached AMP page for/cc @lswang1618