Closed Bug 1751547 Opened 2 years ago Closed 2 years ago

WARNING: Rejected attempt to change type of pref extensions.formautofill.creditCards.available's user value from bool to string

Categories

(Toolkit :: Form Autofill, defect, P2)

defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox-esr91 --- unaffected
firefox96 --- unaffected
firefox97 --- wontfix
firefox98 --- wontfix
firefox99 --- fixed

People

(Reporter: cpeterson, Unassigned)

References

(Regression)

Details

(Keywords: regression)

When running some tests locally (such as mach test browser/components/resistfingerprinting/test/browser/browser_navigator.js), I see the following warning logged to the terminal:

0:03.98 GECKO(45176) [Parent 45176, Main Thread] WARNING: Rejected attempt to change type of pref extensions.formautofill.creditCards.available's user value from bool to string: file mozilla-central/modules/libpref/Preferences.cpp:1633

The pref extensions.formautofill.creditCards.available pref is defined with type bool:

https://searchfox.org/mozilla-central/rev/edd7216defa35b4f64ff6d4332c8dad35fe7b86f/modules/libpref/init/all.js#4606

But some tests' browser.ini or user.js files try to set the pref to the string "on":

https://searchfox.org/mozilla-central/search?case=true&q=extensions.formautofill.creditCards.available

Has Regression Range: --- → yes
Flags: needinfo?(sgalich)

:tgiles looks like we need to update one more place?

Flags: needinfo?(sgalich) → needinfo?(tgiles)

It looks like this will be fixed once I land Bug 1745248. I'm going to mark this bug as dependent on Bug 1745248 so that we can verify this error doesn't appear after that work lands.

Depends on: 1745248
Flags: needinfo?(tgiles)
Severity: -- → S4
Priority: -- → P2

Tim, could you confirm that Bug 1745248 fixed this issue? Thanks

Flags: needinfo?(tgiles)

Not seeing the issue reproduce given the steps in Comment #0, safe to say this issue is fixed.

Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(tgiles)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.