Fast lightweight loading attribute polyfill about image HOT 6 CLOSED

For the meantime, if you don't care too much about backwards-compability (which for me is fine.. because missing lazy-loading is not breaking the site. Having lazyloading is a progressive enhancement to me) you can just add :lazy="false" loading="lazy" as props to the component-call.

That said, I really would love to see that this component moves from a custom lazy-loading to the native one. The main argument to me really is SEO as crawlers (and also stuff like facebook) would not be able to see the images in the current implementation.

from image.

@Suven yeah, it would be great to see this component become the new Nuxt standard for using images, similar to how Next deprecates standard img tag in favor of https://nextjs.org/docs/api-reference/next/image

from image.

We do not plan to support a polyfill for loading=lazy as this is now broadly supported: https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/loading#browser_compatibility.

You can of course always add your own polyfill...

from image.

@danielroe sometimes it just requires to wait for 4 years to resolve the issue, right? 😂

from image.

To me this polyfill looks strange since it requires generation of noscript which has known SSR issues vuejs/vue#8996 . I think it's better to do something similar to what is done in vanilla-lazyload - it uses native lazy load and falls back to IntersectionObserver if native is not supported

from image.

I guess! Though in reality this probably could have been closed with the release of v1.

from image.