*Maciej wrote:* - I couldn’t find a spec for a lazy loading feature policy either, and the Chrome Platform Status page for it gives the status as “removed”[2] so this too might be a nonstandard thing. Or maybe there is a newer (Doesn’t look like the feature policy aspect is in your patch though.)
I hope I am not being too nitpicky. I do think this is a great feature. I just want to make sure we’re cautious about the line between implementing standards-track stuff vs copying things from Chromium that are nonstandard or unspecified (so far). It’s also really worrisome if Chrome implemented semantics for the “loading” attribute beyond what is in the PR, as that will make interop a challenge. Regards, Maciej Just to circle back to this, the current spec PR does not include the "auto" attribute, so there is no need for any Feature/Document policies to control the default image- or frame-loading. The `loading` attribute has two values "lazy" and "eager", and the missing/invalid-value default is "eager". Long-term, Chrome is interested in exploring making the default "lazy". However, we're thinking a good intermediate step is in the future, add "auto" back to the spec and introduce a Document or Feature Policy that allows developers to specify that "auto" == "lazy". Then over time, we may consider simply making the default "lazy". There has been discussion/proposals for image- and frame-policies [1] [2]. There has not been many updates to the proposals, so I am not sure how reliable the current text is. Furthermore, there is a tracking issue for Chrome [3] which covers some implementation discussion for these policies, however it too seems stalled. FYI Chrome currently ships the "auto" attribute, but it is treated as "eager" unless the user has opted into Lite mode, as Thomas mentioned. [1]: https://github.com/w3c/webappsec-feature-policy/blob/master/policies/loading-image-default-eager.md [2]: https://github.com/w3c/webappsec-feature-policy/blob/master/policies/loading-frame-default-eager.md [3]: https://bugs.chromium.org/p/chromium/issues/detail?id=949683
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
