Block fingerprinting Disabled preference doesn't get set when the #brave-show-strict-fingerprinting-mode flag is Disabled

[stephendonner]

Description

Block fingerprinting Disabled preference doesn't get set when the #brave-show-strict-fingerprinting-mode flag is Disabled

(Found while testing #31229.)

Steps to Reproduce

1. install 1.62.59
2. launch Brave
3. open brave://settings/shields
4. set Block fingerprinting to Disabled
5. set brave://flags/#brave-show-strict-fingerprinting-mode to Disabled
6. click Relaunch
7. open brave://settings/shields

Actual result:

Block fingerprinting is toggled to On/Enabled

Expected result:

Block fingerprinting should be toggled to Off/Disabled

Reproduces how often:

100%

Brave version (brave://version info)

Brave | 1.62.59 Chromium: 119.0.6045.163 (Official Build) nightly (x86_64)
-- | --
Revision | e1b8145b091a14990d50127dc7ac0c407f8a13a6
OS | macOS Version 14.2 (Build 23C5047e)

Version/Channel Information:

• Can you reproduce this issue with the current release? No
• Can you reproduce this issue with the beta channel? No
• Can you reproduce this issue with the nightly channel? Yes

cc @arthuredelstein @rebron @fmarier @pes @brave/qa-team

[stephendonner]

[stephendonner]

Verified PASSED using

Brave | 1.62.69 Chromium: 119.0.6045.163 (Official Build) nightly (x86_64)
-- | --
Revision | 271270f8302c71e63d6cca16eee5578836d3fd96
OS | macOS Version 14.2 (Build 23C5047e)

Followed my original steps to reproduce

Confirmed Block fingerprinting was set to Off/Disabled

example	example	example

[stephendonner]

Verified PASSED using

Brave | 1.62.74 Chromium: 119.0.6045.163 (Official Build) nightly (64-bit)
-- | --
Revision | 070cd801c60b65bed66cfed719aeab87384ec9b8
OS | Windows 11 Version 21H2 (Build 22000.2538)

example	example	example

[stephendonner]

Verified PASSED using

Brave	1.62.74 Chromium: 119.0.6045.163 (Official Build) nightly (64-bit) 
Revision	070cd801c60b65bed66cfed719aeab87384ec9b8
OS	Linux

example	example	example

[LaurenWags]

@arthuredelstein @pes10k could one of you please add release-notes/exclude or release-notes/include label as appropriate for this one? Thanks!

[pes10k]

done and done!

[stephendonner]

done and done!

it...can't be both include and exclude 😉

[pes10k]

ah, okie, i defer to @arthuredelstein on this then. I'll remove "include"

[arthuredelstein]

(This particular issue is a follow-up that fixes a bug in my implementation of #31229, so it didn't seem to merit a separate item in release notes.)