Closed kalwalt closed 5 years ago
Hi, it's actually AMP that is adding decoding="async"
. It's nothing to do with this plugin :)
More information about the decoding
attribute on the <img>
tag: https://github.com/whatwg/html/issues/1920
Documentation for the <amp-img>
component (if you inspect the example images you can see the decoding="async"
attribute on all of them: https://ampbyexample.com/components/amp-img/
Many thanks @wildlyinaccurate! i can see in ampbyexample page the <img decoding="async"....>
is added between all the <amp-img>....</amp-img>
tags. I received an error in my website in my search.google.com/search-console/amp
The tag 'img' should be replaced with an equivalent 'amp-img' tag.
in more than one my pages but if i run https://www.kalwaltart.it/#development=1 my page is validated without any error. Maybe was a glitch with AMP or maybe the reason was in another part of my code and after was solved. I'm happy with this, so this means my code was ok. Do you think it can be optimized in some way? Could be added to the list of your examples template?
Hi to all, I am using the
jekyll-responsive-image plugin
for my website with AMP feature. My templateresponsive-image.html
is like this:if i add in one of my page this code:
{% responsive_image path: assets/icons/icon-72x72.png %}
is builded by jekyll in this way:
but in the browser instead became:
Why i found the
<img decoding=aync"......>
code inside? The problem is that the tag is not allowed with AMP so i would avoid this. Have you ever encountered this kind of issue? my website is here www.kalwaltart.it and my repo github: kalwalt.github.io Thank you for your attention. Walter