-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue: Ad Calls Prevented When document.body Isn’t Ready #11927
Labels
Comments
this should solve it; #11926 |
Thank you |
1 task
Thank you! |
Do we think this warrants a patch release to 9.4? |
A patch release for version 9.4 makes sense to me since it affects the ability of ad calls to go through. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
In version 9.4 and later, a change was introduced that prevents ad calls from being made if
document.body
isn’t ready. This issue is linked to the changes made in this commit, which added a location method for cross-frame creatives.Affected Version: 9.4+
Introduced in: PR #11863
Test Page: https://30f9d51a.demo-ann.pages.dev/testpage
Steps to Reproduce
Expected Behavior
Ad calls should be made regardless of whether document.body is fully loaded or not and no Uncaught error should be thrown by pbjs
Actual Behavior
When document.body isn’t ready, the following error is thrown, preventing ad calls from going out:
Analysis
Proposed Solution
Ensure that document.body is ready before attempting to call appendChild. A potential solution is to check for the existence of document.body before executing insertLocatorFrame.
The text was updated successfully, but these errors were encountered: