-
Notifications
You must be signed in to change notification settings - Fork 869
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
A bug between lazy-component and v-lazy #453
Comments
hilongjw
added a commit
that referenced
this issue
Feb 19, 2021
feat: split lazy config & import on demand #453
This was referenced Aug 3, 2024
This was referenced Aug 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug & Does not support on-demand import
bug: I want to use v-lazy and lazy-component to achieve such an effect: the image starts to request when the visual window is 20px (v-lazy), and the component does not mount until it enters the visual window (lazy-component), but because of v- lazy and lazy-component use the same option (preLoad), so this effect cannot be achieved(maybe this is a bug).
Does not support on-demand import: I only want to use v-lazy, but have to import useless components such as lazy-conponent lazy-image
PR
I make a pr about this a problem pr
The text was updated successfully, but these errors were encountered: