Risks of native lazy loading with the HTML loading attribute?

Question

Browsers started recently supporting native lazy loading via the loading attribute.

However, many image heavy sites like unsplash.com and pexels.com don't use native lazy loading.

Obviously, not all browsers support native lazy loading, but what are the risks of using loading="lazy" in addition to other options for lazy loading? That is, if you accept that unsupported browsers won't lazy load images, is there any downside to adding loading="lazy" to img tags?

I don't see any. Maybe this one but that is a browser issue which can (and probably will) be solved. — str
– str, Commented Apr 20, 2020 at 6:33
@str thanks for the reply. could you post as answer if this turns out to be the right answer? thanks for the help! — Crashalot
– Crashalot, Commented Apr 20, 2020 at 6:45
@CertainPerformance thanks, deleted comment and sent an email. — Crashalot
– Crashalot, Commented Sep 1, 2020 at 6:50

Ingo Steinke · Accepted Answer · 2020-12-20 09:28:10Z

0

Due to a bug in chrome, the first browser to support native lazyloading, images that have not yet been loaded will be missing in the printout due to this bug.

answered Dec 20, 2020 at 9:28

Ingo Steinke

9804 gold badges19 silver badges38 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Risks of native lazy loading with the HTML loading attribute?

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related