-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
should <amp-img> be lazyload? #72
Comments
@dvoytenko Might be a bug. Have a URL for us to look at? I'm not 100% positive on current behavior (and we massively changed it yesterday), but we should definitely start loading images when everything further up is done. |
I don't have a URL for now. Help if I attach the file? |
Only so much if we don't have the resources. We'll clarify expected behavior. |
Ok, try that url: |
I believe this is basically expected. We actually rewrote everything about this and it landed last night, so current bugs will be replaced by new bugs :) But, having said that, we prioritize resources by their distance from the current viewport. We will still load them when we have nothing else to do. We don't currently do total lazy loading. I think this is something you could bring up in the mailing list. It is mostly a tradeoff between latency and bandwidth use. |
Ok, make sense. I will send this question to group list later. |
amp-img
is loading all images in my page, before user scroll to there. It's correct?Tks
The text was updated successfully, but these errors were encountered: