Test amp-ad works seamlessly when embedded inside of a PWA

[jasti]

Main thing to ensure is that the ads are loaded and viewability pings (active view) are fired for both AMP and non-AMP ads when they are delivered into an AMP page that is embedded inside of a shadow DOM within a PWA.

[lannka]

@choumx do we have an amp-ad example in your PWA shell?

[lannka]

Confirmed with @choumx , 3P ads works: https://choumx.github.io/amp-pwa/content/21.amp.html
Will need to add an example for A4A. @choumx will take a look and see if he has bandwidth for this sprint.

[dreamofabear]

Tested that an AMP and non-AMP ad render correctly without errors on our local PWA app. Try it out by going to http://localhost:8000/pwa?exp=a4a:-1&force_a4a_ctypes=1,2 and clicking on the "A4A" article.

@jasti @lannka Interestingly, I noticed that the AMP ad doesn't always render faster than the non-AMP ad in PWA with 2G network throttling on Chrome. Instead, the ad with the higher viewport position is rendered first. Might be due to shadow DOM streaming.

[jasti]

It's possible we are falling back to using delayed fetch in this case which is not ideal.
@lannka to confirm. Heads-up to @keithwrightbos to consider this case when making FF work for canonical.

[dreamofabear]

Reassigning to @lannka per comment above. Let me know if I can help.

[ampprojectbot]

This issue hasn't been updated in awhile. @lannka Do you have any updates?

[powerivq]

@jasti It has been tested, and there are no delay on both types of ads on PWA.

@choumx The layout prioritization has been changed to 1 for ads on PWA and that might explain the sequencing.
#12232

I think it's in a fine state now. Feel free to reopen if there's anything concerning.