amp-embed can become stuck in the loading state after an amp-consent choice is made
See original GitHub issueWhat’s the issue?
An amp-embed
element behind a data-block-on-consent
attribute can fail to load following a choice being made in amp-consent. The element will hang with the spinning icon and no iframe
is inserted into amp-embed
element.
On occasion when this happens it will affect all elements behind data-block-on-consent
including amp-ad
.
It happens most often with amp-embed
and was seen on the Google CDN by a client. When it does happen the affected elements are left in a perpetual loading state.
In the instances where only amp-embed
is affected we can see that amp-consent
correctly passes on the consent details as we can see the consent string value in DFP calls for amp-ad
elements.
Here is a video using iOS simulator that displays the issue with just the amp-embed
failing after making a consent choice.
Note that this only happens on the first visit as a new user, once refreshed everything works as expected and that we see no issues with amp-embed
loading.
How do we reproduce the issue?
The original internal reporter spotted it on the Google CDN but as a team we haven’t been able to recreate it by happenstance. We can however recreate it on occasion using a private/incognito tab on an iOS device.
- Visit the above article on the Google CDN in iOS safari with a new incognito/private tab. You’ll need to be using an EU connection for amp-consent
- Hit the the green
Got it
button. - Once the overlay has disappeared scroll down to the end of the article after the social sharing bar and comments block to the taboola amp-embed.
- Note on occasion that the
amp-embed
will just hang with the amp loading icon.
What browsers are affected?
iOS safari/chrome
Which AMP version is affected?
2011252111003
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:5 (4 by maintainers)
I will close this issue for now, but please reopen if it crops up again.
No recent consent changes come to mind. Would be interested to see if this issue pops up again in the near future.