-
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
amp-carousel : images load intermittently #27036
Comments
@alanorozco : any possible workarounds that I can use until this gets fixed? |
I seem to be having the exact same issue. I'm very consistently getting missing images in the carousel. After scrolling through the entire gallery using the loop attribute and repeating the image will appear. This doesn't happen with v0.1. It seems to happen randomly I think it's an image lazyloading issue. Watching the network tab in chrome I see the image load, but it's blank in the carousel. Also I thought this was a Chrome issue only, but I've seen it happen once on iOS as well when opening a private tab. I'm going to switch back to v0.1 for now, but if anyone wants to test this live I can make a test page. |
I'm done some more testing on this issue. It seems to be related to the amp-carousel that is generated by Jetpack. Can someone do some testing with amp-carousel v2 and the jetpack gallery? I've switched to using the code generated from a standard wordpress gallery and just adding the loop and autoplay attributes to get the same functionality as the Jetpack gallery. Adding the code manually I no longer get missing images in the slideshow. |
I can reliably regularly (if yet sporadically) reproduce this issue on: https://www.ryansmithphotography.com/ Here's a screen capture showing the problem after several reload attempts: https://youtu.be/nBtjBtai8s0 This may be a similar issue to #26952. @jridgewell @choumx Is this Resources bug? Will it be fixed by IntersectionObserver? |
Thanks for checking this issue. Like I mentioned I've never seen this
issue when adding the amp-carousel in directly with code in an html block.
So I don't know if there is something different with the way the block is
loaded with jetpack.
…On Wed, Sep 16, 2020, 8:58 PM Weston Ruter ***@***.***> wrote:
I can reliably regularly (if yet sporadically) reproduce this issue:
https://www.ryansmithphotography.com/
Here's a screen capture showing the problem after several reload attempts:
https://youtu.be/nBtjBtai8s0
This may be a similar issue to #26952
<#26952>.
@jridgewell <https://github.com/jridgewell> @choumx
<https://github.com/choumx> Is this Resources bug? Will it be fixed by
IntersectionObserver?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#27036 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB2Y5H7MZ5HCXX573OBGIFTSGFNKHANCNFSM4K66A5SQ>
.
|
Hi @rsmith4321, thanks for the report! After investigating, I'm convinced this is caused by a bug in newly launched experiment. The bug fix was merged in #30188, and will rollout to production tomorrow. |
I'm still able to recreate the issue by doing an empty cache reload. I've also noticed this issue for many months when I use the jetpack carousel so I don't think it's anything recent. I've never seen the issue adding an amp-carousel in an html block. Thanks. |
Wow, this is strange. The amp-img failed to upgrade to the Reopening, setting to a higher priority. /cc @dvoytenko |
When an unlayout (eg, when carousel swipes away) occurs before an unlayout, we can get into a broken state where we _think_ we're fully laid out but in reality we've performed the unlayout. There's still race conditions in each component, since they need to track their own layout/unlayout state. We should quickly migrate to Bento where this isn't an issue. Fixes ampproject#27036 Partial ampproject#13838
When an unlayout (eg, when carousel swipes away) occurs before an unlayout, we can get into a broken state where we _think_ we're fully laid out but in reality we've performed the unlayout. There's still race conditions in each component, since they need to track their own layout/unlayout state. We should quickly migrate to Bento where this isn't an issue. Fixes ampproject#27036 Partial ampproject#13838
* Fix race condition with layout -> unlayout When an unlayout (eg, when carousel swipes away) occurs before an unlayout, we can get into a broken state where we _think_ we're fully laid out but in reality we've performed the unlayout. There's still race conditions in each component, since they need to track their own layout/unlayout state. We should quickly migrate to Bento where this isn't an issue. Fixes #27036 Partial #13838 * Rename variable * Throw cancellation errors where appropriate * Review fixes * Fix dep requirement * Fix sourcemap check * Fix tests * Only allow missing signal param in test mode * Do not report missing abortController Since we're clearing it out after layout completes, it won't exist when we eventually unlayout * Toggle amp-analytics visibility _after_ layout * Fix method call * Fix test * lint * Fix test
Is there is way to know when this update will be live? Do we have to wait for a version 0.3 of the amp-carousel? Thanks! |
It will be live in beta (1% of users) tomorrow afternoon, and production (100%) next Tuesday. |
* Fix race condition with layout -> unlayout When an unlayout (eg, when carousel swipes away) occurs before an unlayout, we can get into a broken state where we _think_ we're fully laid out but in reality we've performed the unlayout. There's still race conditions in each component, since they need to track their own layout/unlayout state. We should quickly migrate to Bento where this isn't an issue. Fixes ampproject#27036 Partial ampproject#13838 * Rename variable * Throw cancellation errors where appropriate * Review fixes * Fix dep requirement * Fix sourcemap check * Fix tests * Only allow missing signal param in test mode * Do not report missing abortController Since we're clearing it out after layout completes, it won't exist when we eventually unlayout * Toggle amp-analytics visibility _after_ layout * Fix method call * Fix test * lint * Fix test
What's the issue?
I am using amp-carousel-0.2.js, however, images in the tag fail to load 1/5 attempts.
How do we reproduce the issue?
Another way to produce, start Chrome on iOS in incognito mode:
The above is repeatable everytime u close all incognito windows on Chrome on iOS.
What browsers are affected?
All browsers on mobile.
Which AMP version is affected?
AMP version: 2002192257490
AMP carousel: https://cdn.ampproject.org/v0/amp-carousel-0.2.js
Is this a new issue? Or was it always broken? Paste the version of AMP where you saw this issue.
Experiencing for first time related to the above page.
The text was updated successfully, but these errors were encountered: