-
Notifications
You must be signed in to change notification settings - Fork 908
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
Tie CSP rule injection to Shields ads/tracker setting #9053
Conversation
aad75dd
to
f7dcfde
Compare
browser()->tab_strip_model()->GetActiveWebContents(); | ||
|
||
auto res = EvalJs(contents, "await window.allLoaded"); | ||
ASSERT_EQ(true, EvalJs(contents, "!!window.loadedNonceScript")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ASSERT_TRUE()
personally i prefer EXPECT_TRUE
Verification PASSED on
Test Cases for brave/brave-browser#16283Verified the STR/Cases outlined via #9053 (comment) as per the following:
Test Cases for brave/brave-browser#16251Verified the STR/Cases outlined via #9053 (comment) as per the following:
|
Verification PASSED using
Verified the STR/Cases outlined via #9053 (comment) as per the following: |
Resolves brave/brave-browser#16283
Resolves brave/brave-browser#16251
Submitter Checklist:
QA/Yes
orQA/No
;release-notes/include
orrelease-notes/exclude
;OS/...
) to the associated issuenpm run test -- brave_browser_tests
,npm run test -- brave_unit_tests
,npm run lint
,npm run gn_check
,npm run tslint
git rebase master
(if needed)Reviewer Checklist:
gn
After-merge Checklist:
changes has landed on
Test Plan:
Fix for brave/brave-browser#16283
Note the test plan from #8281:
This behavior should hold when Shields are up and ads/trackers blocked setting is either standard or aggressive mode. When Shields are down, or ads/trackers are allowed, the above should no longer be observed.
Fix for brave/brave-browser#16251
From brave/brave-browser#16251 (comment):