-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Help the HTML standard with the approach for when to load lazy images #769
Comments
@zcorpan: But there is native standard yet to contain/cover the image into parent element on client-side? This is the main use-case for lazysizes in my projects. |
Like the CSS object-fit property? |
@zcorpan: Yes! With dynamic content the element height cannot be known in advance (well with some complicated server-side browser rendering maybe, but this will still not take the text breaking hyphens, etc into account). Therefore |
Is it something the "auto sizes" feature in lazysizes enables? I don't really follow, a demo might help. |
OK, then I think the following issues cover the needs of @strarsis demo: whatwg/html#4654 The |
@zcorpan |
@aFarkas no such plan currently AFAIK. Browsers can choose to cap their "x" to avoid downloading unnecessarily large images though when choosing from |
https://github.com/aFarkas/lazysizes#what-makes-lazysizes-so-awesome
Lazy-loading images was recently added as a native feature to HTML, and browsers are currently trying to figure out when lazy images should start loading.
Would the maintainers of this project be willing to chime in here: whatwg/html#5408 and explain the approach taken here in more detail, and the rationale? I think this can help inform what browsers should do for
loading=lazy
images.Thanks! ❤️
The text was updated successfully, but these errors were encountered: