Skip to content
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

TCFv2: potential bug - null passed as argument instead of undefined or [] #5510

Closed
jbartek25 opened this issue Jul 17, 2020 · 4 comments · Fixed by #5505
Closed

TCFv2: potential bug - null passed as argument instead of undefined or [] #5510

jbartek25 opened this issue Jul 17, 2020 · 4 comments · Fixed by #5505

Comments

@jbartek25
Copy link
Contributor

Type of issue

Bug or spec clarification

Description

The CMP API of our provider Onetrust doesn't work with Prebid when fetching consent inside an iframe. The reason is that Prebid sends parameter=null in the code here. Onetrust team argues that null is not a valid value and in order to declare no value for parameter it has to be set to either undefined or []. I checked the IAB TCFv2 spec and there's no explicit statement for or against null. Which end should be fixed? Prebid or the CMP?

@jaiminpanchal27
Copy link
Collaborator

@jbartek25 Thanks for opening up issue. Can you share the link of IAB spec as well ? We will look into this and update you.

@smenzer
Copy link
Collaborator

smenzer commented Jul 21, 2020

This looks to be addressed with #5505

@smenzer smenzer linked a pull request Jul 21, 2020 that will close this issue
1 task
@jbartek25
Copy link
Contributor Author

Agreed. Closing. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants