Re: [w3ctag/design-reviews] LazyLoad (loading= attribute) (#361)

Hey everyone, I've taken over the current spec PR, and the latest discussion has left its direction in a better state. 

Here are some updates for this thread:
 - Per spec, images and iframes automatically have the "auto" LazyLoad state. This allows UAs to defer these, unless they are in-viewport, or not [connected](https://dom.spec.whatwg.org/#connected) (in the DOM sense). This means that when these elements are created from JavaScript, they will not be deferred, which was the biggest thing folks were concerned about in situations like Jake's comment, for compatibility
 - The latest spec review happens to align the spec very closely to Chrome's implementation, which is just about [ready to ship](https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/jxiJvQc-gVg/wurng4zZBQAJ). We've been landing [WPTs](https://github.com/web-platform-tests/wpt/tree/master/loading/lazyload) for this as well.
 - I will be updating the spec soon, to address the latest review

Let me know if I can clarify anything/provide more info

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/361#issuecomment-515333110