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

fixed width container+ mobile #129

Open
pruttned opened this issue Jan 31, 2017 · 5 comments
Open

fixed width container+ mobile #129

pruttned opened this issue Jan 31, 2017 · 5 comments

Comments

@pruttned
Copy link

Hi,
I have issue with images in long horizontal fixed width div in mobile browser (tested on chrome 54.0.2840.85 and also in chrome dev tools).
Images are not loaded during horizontal scrolling even when they are in viewport. Only images at the beginning are loaded and other images only when the viewport is far pass them on the right.

I’ve created plunk with the issue http://run.plnkr.co/plunks/CsERqAApIppUzugTY8px/
(http://plnkr.co/edit/CsERqAApIppUzugTY8px)
In order to reproduce, it is necessary to open dev tools and select any mobile device in the device toolbar (e.g. Nexus 5X). Then refresh the page.

Thanks.

@dinbror
Copy link
Owner

dinbror commented Feb 19, 2017

Hey @pruttned

You need to define the container on initialize: http://dinbror.dk/blazy/examples/#image-inside-container
Sorry for the late reponse

@pruttned
Copy link
Author

Hi.
Thanks for your response, but I'm not using a scrolling container.
It is just a wide row of images and whole window is scrolled.
But it seems, that the problem is with getBoundingClientRect because it somehow returns constant result even when the windows is scrolled.
So maybe it is bug in Chrome, or maybe I'm doing something terribly wrong :)

@dinbror
Copy link
Owner

dinbror commented Mar 1, 2017

@pruttned

ahh sorry about that. Do you still see the issue. Just tested in chrome 56.0.2924.87 and can't reproduce it.

@pruttned
Copy link
Author

pruttned commented Mar 1, 2017

Hi,
yes, I'm still able to reproduce this issue as you can see on the picture.

image

Thanks.

@qbitza
Copy link

qbitza commented Nov 28, 2017

Any work around for this?

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

No branches or pull requests

3 participants