Stop reporting window.postMessage AsyncTasks to AdTracker
What: Stop reporting the AsyncTask from LocalDomWindow::DisaptchPostMessage() to the ad tracker. Why: A common loading flow for pages is: - show an ad in an iframe - wait for a postmessage from the ad to indicate it has finished - render some content Currently, anything a non-ad script does in response to a postMessage from an ad iframe gets considered an ad. We would like to use the ad status of the script processing the postMessage as a sole indicator of whether an ad is being created, rather than the frame the message was sent from. This is only an issue for same-renderer postMessages, as we currently do not route any information alongside the messages sent to a different renderer. Bug: 1127829 Change-Id: Id3e5e8c9fa313ad50fa915c28114c7fc11bbc1f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2416747 Commit-Queue: John Delaney <johnidel@chromium.org> Reviewed-by:Nate Chapin <japhet@chromium.org> Reviewed-by:
Josh Karlin <jkarlin@chromium.org> Cr-Commit-Position: refs/heads/master@{#808980}
Showing
Please register or sign in to comment