Chrome 65+ allows synchronous XHR to be disabled. Blocking the UI thread on the network is a perf anti-pattern and so should probably not be allowed in AMP documents or embeds.
Chrome for now, but at TPAC all other browsers indicated a desire to add this feature as a first step of trying to phase-out sync-xhr.
All
/cc @clelland @cramforce with whom this has been discussed offline.
I think we should launch this for amp-ad and amp-iframe.
@lannka Could you take this on?
to @jastiv for prioritization.
Given current commitments, it looks like we'll tackle this in the second half of April.
CC @zhouyx
I'll try to implement on my flight back from Australia. I'll implement behind an experiment and then we can see how we can ship it.
@cramforce did you have a chance to look at this? If not, we can probably reassign to someone on the ads team.
Turned this on in canary 5 minutes ago in #16524
Implementation in #14481
Shipping this with our next prod release. Let's see how it goes :)
Shipped yesterday 馃帀
Most helpful comment
Shipped yesterday 馃帀