🌸 Cherry-pick request for #28994 into #2006152249000 (Pending)

[zhouyx]

Cherry-pick request

Issue	PR	Beta / Experimental?	Stable?	LTS?	Release issue
#28994	#28988	Yes	No	No	#<RELEASE_ISSUE>

Why does this issue meet the cherry-pick criteria?

The issue is causing us from reporting visibility even if the AMPHTML ad is below the folder when the iframeClient doesn't exist (rendered in a friendly iframe)

Mini-postmortem

TODO: This postmortem will be written after the cherry-pick deployment and before this issue is closed. Delete this TODO when the postmortem is ready.

Summary

<1-2 sentences summarizing the problem and root causes.>

Impact

• <Which users were affected? Roughly how many?>
• <How were users affected? E.g. partial or complete loss of functionality?>

Action Items

• #<ISSUE_NUMBER>: <Add unit/integration/end-to-end test>
• #<ISSUE_NUMBER>: <Add monitoring for edge case via error logging>
• #<ISSUE_NUMBER>: <Refactor an easily misused API>

---

/cc @ampproject/release-on-duty @ampproject/wg-approvers @ampproject/cherry-pick-approvers

[zhouyx]

The ads team used 2006152249000 as RC, which is not RC for AMP docs (2006112352000). Maybe we could cherrypick to 2006112352000 instead and have them changed RC version to that.

[dvoytenko]

Approved.

[zhouyx]

to @jeffkaufman and @jridgewell
Since the issue is inabox only, we can do it either way

1. Perform a cherrypick to nightly build 2006152249000. (inabox RC version)
   or
2. Perform a RC cherrypick to 2006112352000 (AMP RC version), and set the inabox RC to this version.

[jeffkaufman]

We would be happy with either (1) or (2). Whichever you prefer!

Thanks for fixing this!

[zhouyx]

Instead, we agreed to proceed with the new nightly build 2006230309000. Closing the cherry-pick request.