Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Fix default setting behavior for getSetting() #4988

Merged
merged 1 commit into from
Oct 20, 2016
Merged

Fix default setting behavior for getSetting() #4988

merged 1 commit into from
Oct 20, 2016

Conversation

bsclifton
Copy link
Member

@bsclifton bsclifton commented Oct 20, 2016

I accidently introduced the bug here (merged into 0.12.6):
889757e#commitcomment-19471078

The fix by @darkdh is correct, except password manager defaults to a null value (rather than undefined)
1092758

This fix checks against both undefined and null

Auditors: @darkdh @bbondy

Test Plan: run unit tests (most PW manager ones were failing)

I accidently introduced the bug here (merged into 0.12.6):
889757e#commitcomment-19471078

The fix by @darkdh is correct, except password manager defaults to a null value (not undefined)
1092758

This fix checks against undefined and null

Auditors: @darkdh @bbondy

Test Plan: run unit tests (most PW manager ones were failing)
@bsclifton bsclifton merged commit 92b3485 into brave:master Oct 20, 2016
@bsclifton bsclifton deleted the fix-default-setting branch October 20, 2016 08:58
@darkdh
Copy link
Member

darkdh commented Oct 20, 2016

++

@luixxiul luixxiul added this to the 0.12.6dev milestone Oct 21, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants