~0.1% of pages in @HTTPArchive are using <iframe loading=lazy> (or auto). This is bad. Don't use features that aren't ready! Ready = in the spec and supported by 2+ browser engines.
https://docs.google.com/spreadsheets/d/1EZ8XQr9LMzkpY8n0stKcXdyVHswox6rzk2sDFdHjqNk/edit?usp=sharing …https://twitter.com/zcorpan/status/1237016679667970050 …
-
-
~ “Please note <iframe loading=lazy> is currently non-standard. While implemented in Chromium, it does not yet have a specification and is subject to future change when this does happen. Take great care when using it”. Something like that?
-
PR up that addresses this (for both <iframe loading="lazy" and the "auto" value):https://github.com/GoogleChrome/web.dev/pull/2421/files …
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.