Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'importance' + 'loading' attributes #699

Open
Malvoz opened this issue Sep 25, 2018 · 8 comments

Comments

@Malvoz
Copy link
Contributor

commented Sep 25, 2018

@sideshowbarker

This comment has been minimized.

Copy link
Member

commented Oct 5, 2018

In general as far as allowing new attributes, it seems better to wait until at least two different browser engines support them. At this point, importance is only supported in Blink, right? And lazyload is only supported in Edge?

@sideshowbarker

This comment has been minimized.

Copy link
Member

commented Oct 5, 2018

Actually, stepping back even further: What should happen first for both these cases is that the editors of those specs creates patches that integrate the attribute definitions directly into the HTML spec, and submit PRs at https://github.com/whatwg/html with the patches

@Malvoz Malvoz changed the title 'importance' + 'lazyload' attributes 'importance' + 'loading' attributes Apr 7, 2019

@DamonHD

This comment has been minimized.

Copy link

commented Apr 19, 2019

FYI:

https://twitter.com/addyosmani/status/1114777583302799360

Native lazy-loading is coming to the web! (link: https://bit.ly/loading-attribute) bit.ly/loading-attrib…<img loading=lazy>defers offscreen images until the user scrolls near them. Shipping in Chrome ~75 (link: https://bit.ly/loading-i2s)

loading=lazy

now due this month (May).

@DamonHD

This comment has been minimized.

Copy link

commented May 18, 2019

https://tiny.pictures/guide/native-lazy-loading

"Beginning with version 75 (available as preview version now, beta in May, stable on 04th June 2019), Chromium and Google's Chrome browser will be shipped with a native lazy-loading mechanism enabled by default."

Note that since Edge is switching to using Chromium then it will support loading=XXX too.

@nschonni

This comment has been minimized.

Copy link
Member

commented May 18, 2019

I don't think Chromium Edge will count as a second browser, same as Opera doesn't count as a second implementation when they did the same years ago

@DamonHD

This comment has been minimized.

Copy link

commented May 18, 2019

OK!

But I'm itching to get the loading=lazy tags on all my below-the-fold images regardless. For a number of my longer pages weight will be significantly reduced for some users, I think.

Rgds

Damon

@DamonHD

This comment has been minimized.

Copy link

commented May 20, 2019

If I wanted to jump the shark here, I guess that I could hack the relevant lines into:
validator/schema/html5/embed.rnc
and learn how to build myself the vnu.jar. I doubt I have the time for that as soon as I'd like to try 'loading=lazy'. Is there some "please don't look at the attributes in tag XXX too closely" flag that I can use in the meantime?

Rgds

Damon

@DamonHD

This comment has been minimized.

Copy link

commented Aug 14, 2019

While complaining to various people at Google how it had stopped working, I pulled the very latest mainline Chrome and it does now seem to have a full working loading=lazy implementation as of 76.0.3809.100.

See test page (load over slow-ish network): http://www.earth.org.uk/img/WW-PV-roof/EVAnalysis201210/

And BTW, it works very nicely on this somewhat extreme case.

Rgds

Damon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.