Amphtml: AMP Experiment Takes a While to "Switch On"

Created on 9 Apr 2018 · 13Comments · Source: ampproject/amphtml

What's the issue?

Heya AMP team,

We've noticed that amp x intermittently fails to "switch on" - it takes a couple of refreshes to get it working.

I've been able to verify the above from the following:

"amp-x-experiment-name='the-variant'" is not always set in the body tag
~AMP.isExperimentOn() returns false~

Feedback on this highly appreciated. 🙂

How do we reproduce the issue?

N/A (In development, requires authorisation), sorry.

What browsers are affected?

All browsers.

Which AMP version is affected?

AMP - https://cdn.ampproject.org/v0.js
AMP Experiment - https://cdn.ampproject.org/v0/amp-experiment-0.1.js

Knowledge share on SO

https://stackoverflow.com/questions/49672039/amp-experiment-fails-to-switch-on

Bug analytics

Source

akabiru

Most helpful comment

Thanks all for the help! Happy to report back that the experiment is working correctly on our sites. 🎉

briankabiro on 11 Sep 2018

🎉1 👍1

All 13 comments

@choumx Can you comment on whether this is expected?

rsimha on 10 Apr 2018

Ah, I think there's some confusion due to a naming collision. AMP.isExperimentOn is for internal features listed here and is unrelated to the amp-experiment extension.

choumx on 10 Apr 2018

@rsimha @choumx thanks for the response. AMP.isExperimentOn() was as an example; my bad. Are you able to comment on why AMP X does not always switch on on first load?

akabiru on 10 Apr 2018

There might be a small latency after page load for the amp-experiment extension to load etc.

Do you have a sample page that is exhibiting this behavior?

choumx on 10 Apr 2018

Thanks for reopening the issue @choumx. I'm afraid I'm unable to share the asset here as it's still in development/requires authorisation.

I've made a quick pen here https://jsbin.com/kivuxid/edit?html,output for a sample of what we're looking at.

So far I'm ruling out the following:

does the number of amp components being loaded affect this in some way (we have 6 amp component scripts)
Toggling to a slow 3G connection makes amp-x to fail - guess due to the latency issue

akabiru on 11 Apr 2018

Thanks for the jsbin. I can't reproduce amp-x-foo-bar-experiment not being set on the <body> even with network throttling, and look at the source code I don't see a timeout. As long as the fetch of the amp-experiment extension itself completes, this should work.

choumx on 11 Apr 2018

/cc @lannka

choumx on 11 Apr 2018

hmm, no worries. I'll see if there's any other way I can reproduce the issue. Cheers! 👍

akabiru on 11 Apr 2018

Thanks and good luck!

choumx on 11 Apr 2018

👍1

_Cross-sharing this from slack._

Hello
I’m reaching out to provide another sample amp document for use in resolving this issue,as raised by Austin.

Since the actual sample amp document requires credentials, that we aren’t able to share, to access, I have copied the raw html on the amp document, returned by accessing the link in the steps below.

The validator shall report errors for this webpage because of the inline style
clauses found in the raw html.

Please use the steps below to view the reported issue and advise on how we should proceed to have the issue resolved.

Steps to reproduce
1.On a new tab, on chrome, open developer tools and toggle device toolbar.
2.Select Mobile L - 425px
2.Go to https://a-referrer.000webhostapp.com/amp-experiment/indonesia.html

The steps outlined above, return a page with a working amp experiment, when carried out in an incognito window.

Below are screen grabs for the page above as seen on a normal window, incognito window and iPhone 6s safari respectively.

normal window - chrome
normal_window