Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Ovo će web mjesto raditi na ograničen način, dok obavljamo održavanje stranice. Ako neki članak ne riješi tvoj problem i ako želiš postaviti pitanje, naša zajednica za podršku spremna je pomoći na Twitteru @FirefoxSupport i na Redditu /r/firefox.

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

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

  • 1 odgovor
  • 1 ima ovaj problem
  • 1 prikaz
  • Posljednji odgovor od TyDraniu

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).

Svi odgovori (1)

more options

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