Skip to content
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

In Safari OSX offset option does not load images in view port after page load #66

Closed
philspbr opened this issue Nov 3, 2015 · 6 comments

Comments

@philspbr
Copy link

philspbr commented Nov 3, 2015

I have a problem when using Safari/OSX and the offset option: The images in the view port do not get loaded on document.ready.
In my case I used offset: 200 and while the images in the view port appear on my Desktop PC using Chrome, IE or Firefox, they do not appear on my MBP Retina using the latest Safari browser. Only after scrolling up and down and having loaded all the other images, they appear.
I called the plugin like this:
jQuery(document).ready(function() {
var bLazy = new Blazy({
selector: '.thumbnail',
offset: 200
});
});

@dinbror
Copy link
Owner

dinbror commented Nov 4, 2015

Hey @philspbr .

Do you have a live example? Do you see the same issue on my demo page: http://dinbror.dk/blazy ?

@dinbror
Copy link
Owner

dinbror commented Dec 20, 2015

hey @philspbr

Friendly ping

@alimony
Copy link

alimony commented Feb 10, 2016

@dinbror I see this behavior on http://scifiagenda.com but only when reloading the page (i.e. cmd-R) not when revisiting the page, for example focusing the address field and pressing enter. Really strange.

@alimony
Copy link

alimony commented Feb 10, 2016

Actually, I just pushed a workaround so you won't see the buggy behavior on that URL anymore. This is what I did:

(function() {
    var bLazy = new Blazy({
        offset: 300
    });
    window.setTimeout(function () {
        bLazy.revalidate();
    }, 1);
})();

@dinbror
Copy link
Owner

dinbror commented Mar 6, 2016

Fixed in v. 1.5.4

@dinbror dinbror closed this as completed Mar 6, 2016
@philspbr
Copy link
Author

Hi dinbror, sorry for the late response! I tested v.1.5.4 and it is fixed. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants