UPDATE [May 14 2020]
I'm pretty sure that the AMP team will spent another 5 years on decision "TO DO vs NOT TO DO". The workaround is simple - use iframe with JS code inside which calls history.back. Yes it's ugly but it works.
Can you please add some param for <button> or <a> tags which will do javascript:window.history.back() call?
I use amp-iframe as workaround for this issue, but it will be much more convenient to have dedicated "amp-" tag for it or an attribute for <button> or <a> tags.
Thank you in advance
UPDATE [May 14 2020]
I'm pretty sure that the AMP team will spent another 5 years on decision "TO DO vs NOT TO DO". The workaround is simple - use iframe with JS code inside which calls
history.back. Yes it's ugly but it works.Can you please add some param for
<button>or<a>tags which will do javascript:window.history.back() call?I use amp-iframe as workaround for this issue, but it will be much more convenient to have dedicated "amp-" tag for it or an attribute for
<button>or<a>tags.Thank you in advance