Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Wannan tattunawa ta zama daɗaɗɗiya. Yi sabuwar tambaya idan ka na bukatar taimako.

iframe for YouTube embed: lazy loading doesn't work in Firefox

  • 1 amsa
  • 1 yana da wannan matsala
  • 3 views
  • Amsa ta ƙarshe daga TyDraniu

arvindpdmn
arvindpdmn
more options

My system is Firefox 79, Windows 10. Lazy loading is supported in Firefox since version 75: https://caniuse.com/#feat=loading-lazy-attr

I found that this works on Firefox for lazy loading of images. However, YouTube embedding in an iframe, it doesn't work. I ensured that the video is long way below the fold. Even then, the iframe is loaded upfront. This is the HTML for the iframe:

<iframe loading="lazy" src="https://www.youtube.com/embed/iQBat7e0MQs" allowfullscreen="" width="480" height="270"></iframe>

On Chrome, lazy loading works as expected for the same web page (on my localhost).

My system is Firefox 79, Windows 10. Lazy loading is supported in Firefox since version 75: https://caniuse.com/#feat=loading-lazy-attr I found that this works on Firefox for lazy loading of images. However, YouTube embedding in an iframe, it doesn't work. I ensured that the video is long way below the fold. Even then, the iframe is loaded upfront. This is the HTML for the iframe: <iframe loading="lazy" src="https://www.youtube.com/embed/iQBat7e0MQs" allowfullscreen="" width="480" height="270"></iframe> On Chrome, lazy loading works as expected for the same web page (on my localhost).

All Replies (1)

TyDraniu
TyDraniu
  • Top 10 Contributor
more options

Hi, it doesn't work on Firefox yet. You have to follow bug 1622090.