I thought your question was really interesting. Why not lazy everything?? I thought maybe the browser implementer's might have considered this and here is what I could find.
The most relevant section is the "Compatibility risks" from both documents.
Summarizing here if you dont want to read the source material. The risks all seem marginal. The most likely one to have impact to dev.to is change in load pattern in how images are accessed that MAY have an impact on your servers. If you are loading your images from s3 or a cdn I would not expect any impact.
Also if you are doing any analytics via images, counting image loads, or tracking pixels it can mess with statistics. But shrug emoji
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I thought your question was really interesting. Why not lazy everything?? I thought maybe the browser implementer's might have considered this and here is what I could find.
Blink LazyImages (public) Doc
docs.google.com/document/d/1e8ZbVy...
Blink LazyLoad Design Doc (public) Doc
docs.google.com/document/d/1e8ZbVy...
The most relevant section is the "Compatibility risks" from both documents.
Summarizing here if you dont want to read the source material. The risks all seem marginal. The most likely one to have impact to dev.to is change in load pattern in how images are accessed that MAY have an impact on your servers. If you are loading your images from s3 or a cdn I would not expect any impact.
Also if you are doing any analytics via images, counting image loads, or tracking pixels it can mess with statistics. But shrug emoji