-
Notifications
You must be signed in to change notification settings - Fork 889
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
Explicitly set the default view for shield settings #4860
Conversation
kShieldsAdvancedViewEnabled)); | ||
// verify that pref was set (and is not default) | ||
const PrefService::Preference* pref = |
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.
updated test to verify value IS SET 👍
CI passed on all platforms, Windows ran into an issue during |
@bsclifton Thanks for the hustle!! :) |
Defaults to: - advanced for existing users - simple for new users Changing the default was not "locking in" the setting. This change locks in that default. Fixes brave/brave-browser#8533
7e58f3d
to
2ae4fef
Compare
EXPECT_TRUE( | ||
browser()->profile()->GetPrefs()->GetBoolean( | ||
kShieldsAdvancedViewEnabled)); | ||
// verify that pref was set (and is not default) |
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.
I think this test is redundant with above one? what is the purpose of this test?
Each browser tests uses fresh profile.
I assume you want spanning browser test? (https://www.chromium.org/developers/testing/browser-tests)
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.
Goal for this test is to have a non-first-run profile and verify that value does get set and that it's what we expect (advanced) 😄
Versus the one above, which is having an empty first-run profile and then verifying it gets simple view
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.
Oh, I didn't know profile that used for this test is non-first-run profile :)
I thought all browser tests uses fresh test profile.
2ae4fef
to
42f95d4
Compare
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.
++
CI looks good! Only had lint/deps failures which are being addressed in Master too. Good to merge 🎉 |
This was intended to lock in advanced view for existing users and has done its job :) It's now obsolete Fixes brave/brave-browser#12104 This contains a manual revert of #3154 and #4860
Defaults to:
Changing the default was not "locking in" the setting. This change
locks in that default.
Fixes brave/brave-browser#8533
Submitter Checklist:
npm run lint
)git rebase master
(if needed).git rebase -i
to squash commits (if needed).Test Plan:
See brave/brave-browser#8533
Reviewer Checklist:
After-merge Checklist:
changes has landed on.