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
Cards with lazy loading images #354
Comments
Thank you. Native image lazy loading has not yet been applied. We will add it later. |
This issue/PR has been automatically marked as stale because it has not had any update (including commits, comments, labels, milestones, etc) for 30 days. It will be closed automatically if no further update occurs in 7 day. Thank you for your contributions! 한글이 이슈/PR은 commits, comments, labels, milestones 등 30일간 활동이 없어 자동으로 stale 상태로 전환되었습니다. 이후 7일간 활동이 없다면 자동으로 닫힐 예정입니다. 프로젝트 개선에 기여해주셔서 감사합니다. |
No updates, but also not resolved. Just patient waiting here. |
Sorry for the long wait. I am going to start working. I plan to release it with another PR. |
No worries. I consider lazy loading to be more of a nicity then a requirement. |
* feat: support native lazy loading #354 * fix: change ready module * test: test lazy loading * fix: remove useless code * skip: apply review * chore: update imready version * feat: add contentError event * fix: fix destroy method * test: test loading manual test * fix: fix startLoading, endLoading parameter * chore: update imready
|
Works on my machine. I have it queued up to test on a production website later tonight, I'll let you know if I encounter any problems. |
Works great! |
Description
If an element is appended that includes an
img
with theloading="lazy"
attribute. All cards will fail to be laid out. Optimally these elements should be appended and positioned as if they did not have the image (optionally with the width and height applied ahead of time), then re-positioned when the image loads at a later point.Steps to check or reproduce
This can be reproduced using any grid with images:
to (adding
loading="lazy"
)The text was updated successfully, but these errors were encountered: