-
Notifications
You must be signed in to change notification settings - Fork 281
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
Lazyload seems to prevent loading of "visible" images until scrolling begins #669
Comments
when I comment out |
Is this still an issue now that Lazyload has been removed? |
What version of WPRig are you using? LazyLoad has been removed from WP Rig
as of the latest release.
…On Mon, Nov 23, 2020 at 1:25 PM Peter Wennersten ***@***.***> wrote:
when I comment out new Lazyload\Component(), from /inc/Themephp IE11 has
no problem any longer. Also applies to IE10 that refused to show any images
whatsoever before the tweak. I don't know, maybe it's just a collision with
WP 5.5 lazyloading?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#669 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB6LMGOP55SEA4362ALETNLSRKZLDANCNFSM4T74LFSA>
.
--
Rob Ruiz
Owner of Bizzle Designs
Web Design/Graphic Design/Sound Design/Audio & Video Production
www.bizzledesigns.com
|
So I guess it should not be an issue anymore. I was using the current version as of the date when I created this ticket. I have not had the opportunity to verify with the version that is current today.
|
Issue Overview
IE11: Images in visible viewport space are not displayed until scrolling begins
Describe your environment
tested in IE11 on Win8.1 virtual machine from MS EdgeDev.
Steps to Reproduce
Expected Behavior
I expected the image to be displayed without having to scroll.
Current Behavior
The image is not shown until I begin scrolling even though it fits in the viewport.
Possible Solution
Screenshots / Video
Related Issues and/or PRs
The text was updated successfully, but these errors were encountered: