Update browser listener flow to avoid flushing data without consent - #82
Merged
EmilianoSanchez merged 3 commits intoFeb 24, 2022
Merged
Conversation
EmilianoSanchez
force-pushed
the
user_consent_browser_listener
branch
from
February 23, 2022 19:20
5fc7e75 to
7342389
Compare
mmelograno
approved these changes
Feb 24, 2022
Base automatically changed from
user_consent_handle_trackers_and_submitters
to
user_consent_baseline
February 24, 2022 19:38
…consent_browser_listener
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Javascript commons library
What did you accomplish?
How do we test the changes introduced in this PR?
Extra Notes