Native lazy loading has landed in Chrome
1–10 of 49 posts
Re: Native lazy loading has landed in Chrome
#2`if ('loading' in HTMLImageElement.prototype === true) {`
/rolleyes
Re: Native lazy loading has landed in Chrome
#3Edge will pick this up going forward as it is based on Chromium.
Re: Native lazy loading has landed in Chrome
#4English isn't my first language but shouldn't it be "... has landed in Chrome" instead of "... is landed in Chrome"?
Re: Native lazy loading has landed in Chrome
#5As a developer and systems architect, I really like this. As uset, I hate this so much. On slower connections, I like to load a page, swap tabs, come back later and expect the page to be loaded. This mechanism will now break (and is already brokrn by the usr of these lazy loading libs).
Re: Native lazy loading has landed in Chrome
#6Good. I hate lazy loading. I hope they add an option in the browser so I can disable it globally.
Re: Native lazy loading has landed in Chrome
#7I'm happy to see this. So many websites with lazy loading never implemented a fallback for noscript. And most of the popular libraries didn't account for this accessibility.
Re: Native lazy loading has landed in Chrome
#8As a developer and systems architect, I really like this. As uset, I hate this so much. On slower connections, I like to load a page, swap tabs, come back later and expect the page to be loaded. This mechanism will now break (and is already brokrn by the usr of these lazy loading libs).
Hmm, maybe if websites don't use lazy loading JavaScript anymore (guilty as charged btw) then you'll be able to configure it however you want in browser settings?
Re: Native lazy loading has landed in Chrome
#9English isn't my first language but shouldn't it be "... has landed in Chrome" instead of "... is landed in Chrome"?
Yes, you're correct - they should be using "has"
Re: Native lazy loading has landed in Chrome
#10Link could be replaced with the original from which all content was plagiarised?