-
Notifications
You must be signed in to change notification settings - Fork 7
Issues: naver/egjs-imready
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
I want to use an external lazy module instead of loading="lazy".
feature
#30
by daybrush
was closed Dec 24, 2021
The prefix is changed, but skip is not applied.
bug
Something isn't working
#21
by daybrush
was closed Oct 8, 2021
If there is no src, preReady, ready does not occur.
bug
Something isn't working
#19
by daybrush
was closed Apr 14, 2021
Cannot set property 'hasLoading' of undefined
bug
Something isn't working
#16
by daybrush
was closed Jan 11, 2021
Browser coverage needs to be checked like Array#some.
bug
Something isn't working
#13
by mixed
was closed Dec 4, 2020
When loading images and non-loading images are used together, preReady occurs immediately.
bug
Something isn't working
#11
by daybrush
was closed Dec 4, 2020
The timing of loading images is strange.
bug
Something isn't working
#9
by daybrush
was closed Dec 2, 2020
The element has skip attribute, It is excluded from totalCount.
bug
Something isn't working
#4
by daybrush
was closed Dec 2, 2020
The element has loading, but hasLoading property returns false.
bug
Something isn't working
#3
by daybrush
was closed Dec 2, 2020
ProTip!
no:milestone will show everything without a milestone.