You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Update amp-ad-network-doubleclick-impl.md
* Reverting doc changes
The previous change was made in error (wrong branch).
* Address issues #5472 (ensure AmpAdXOriginIframeHandler.init promise is returned as part of layoutCallback) & #5273 (only increment 3p ad throttling when creative known not to be AMP)
* address PR feedback
* Fix lint errors
* fix type check errors
* Add tag to dev info
Lith
pushed a commit
to Lith/amphtml
that referenced
this issue
Dec 22, 2016
* Update amp-ad-network-doubleclick-impl.md
* Reverting doc changes
The previous change was made in error (wrong branch).
* Address issues ampproject#5472 (ensure AmpAdXOriginIframeHandler.init promise is returned as part of layoutCallback) & ampproject#5273 (only increment 3p ad throttling when creative known not to be AMP)
* address PR feedback
* Fix lint errors
* fix type check errors
* Add tag to dev info
Lith
pushed a commit
to Lith/amphtml
that referenced
this issue
Dec 22, 2016
* Update amp-ad-network-doubleclick-impl.md
* Reverting doc changes
The previous change was made in error (wrong branch).
* Address issues ampproject#5472 (ensure AmpAdXOriginIframeHandler.init promise is returned as part of layoutCallback) & ampproject#5273 (only increment 3p ad throttling when creative known not to be AMP)
* address PR feedback
* Fix lint errors
* fix type check errors
* Add tag to dev info
I found that if an A4A decide to render as 3p ad it will call
this.renderViaCrossDomainIframe_
and resolve the#layoutCallback
immediately after that.However in 3PAdImpl, we will only resolve
#layoutCallback
when thisapiHandler.startUp
promise is resolved. https://github.com/ampproject/amphtml/blob/master/extensions/amp-ad/0.1/amp-ad-3p-impl.js#L217I think we should keep the timestamp same in those two cases.
The text was updated successfully, but these errors were encountered: