Skip to content
This repository was archived by the owner on Dec 23, 2020. It is now read-only.

Review whether lazy-loading should cover more than images #3

Closed
felixarntz opened this issue Jan 16, 2020 · 3 comments
Closed

Review whether lazy-loading should cover more than images #3

felixarntz opened this issue Jan 16, 2020 · 3 comments
Labels
help wanted Extra attention is needed

Comments

@felixarntz
Copy link
Member

The current version of the spec proposal does not include any information about loading becoming available on iframe tags. Chrome does support that, but if that is even more experimental and not tied to the spec itself, we should not include it, especially as the primary focus certainly is images.

Let's gather some more information on this and revisit.

@felixarntz felixarntz added the help wanted Extra attention is needed label Jan 16, 2020
@remyperona
Copy link

There is a plan to update the spec for iframe too, but will be done separately, per comment whatwg/html#3752 (comment)

@azaozz
Copy link
Contributor

azaozz commented Jan 17, 2020

Yes, that's my understanding too. Also the auto value for the loading attribute seems to have been dropped from the specs: https://github.com/whatwg/html/pull/3752/files#r344740202.

What would be best to do in WP in that case? Shall we keep the option to auto-add loading="lazy" to iframes, or shall we add it when the specs are ready (or nearly ready)?

Opened #5 to follow up.

@felixarntz
Copy link
Member Author

I've confirmed that inclusion of iframe tags is not planned in this iteration of the spec. It's likely coming in the future, but I think it makes sense for us to exclude iframes from here - especially since the impact of lazy-loading images will be much bigger.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants