Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

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

  • 1 ответ
  • 1 имеет эту проблему
  • 1 просмотр
  • Последний ответ от 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).

Все ответы (1)

more options

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