Closed Bug 1854216 Opened 1 year ago Closed 1 year ago

trr.mode pref set via about:config resets when the browser is restarted

Categories

(Fenix :: General, defect)

Firefox 119
All
Android
defect

Tracking

(firefox117 unaffected, firefox118 unaffected, firefox119 verified, firefox120 verified)

VERIFIED FIXED
120 Branch
Tracking Status
firefox117 --- unaffected
firefox118 --- unaffected
firefox119 --- verified
firefox120 --- verified

People

(Reporter: ale82ale, Assigned: valentin)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [qa-triaged])

Attachments

(1 file)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/119.0

Steps to reproduce:

in fenix nighlt v 119 is no longer possible to permanelty set trr.mode to any value other than zero for example setting to 3 works but if fenix is killed and restarted trr.mode reset to default zero value , BUT SEROUSLY?????????????????????

Actual results:

NIGHLT USER are supposed to change trr.mode without issue

Expected results:

trr.mode reset to 0 at every phone reboot or app restart

Doesn't need to be hidden (it's security-related, but not an attack).

Are you able to save other prefs? It's possible there's a file corruption problem specific to you.

Ah, Andrew found bug 1591533 just landed and may have changed how this works. Might be an unintended regression, or maybe GeckoView (underlying Fenix) created a different way to set these. There are some differences in how Fenix has to work for anything that gets exposed to the front end.

Group: mobile-core-security
Type: enhancement → defect
Keywords: regression
Regressed by: 1591533
See Also: → 1591533

:elizabbennet, since you are the author of the regressor, bug 1591533, could you take a look?

For more information, please visit BugBot documentation.

Flags: needinfo?(elizabbennet)

I tested on 3 different devices so I highly doubt there's file corruption ...

I am able to toggle/ modify some other settings and observe they persist over app restart. Looks like this is a regression because changes from the about:config pages are not propagate to the new api somehow? I am not familiar with how the config page works yet I will try to take a look later this week.

Flags: needinfo?(elizabbennet)

There are some differences in how Fenix has to work for anything that gets exposed to the front end.

I tried to toggle javascript.enabled using the about:config page and confirmed that if a geckoview runtime setting is exposed, GeckoView will reset it after app restart. Although this is an unintended regression, I am reluctant to rollback because it will block non-tech savvy users to have DoH eventually. Would it be possible for Mozilla's Engineers to prioritize bug 1801530 to P1/P2 and provide an Android UI for end-users to toggle TRR properly?

tagging :celu :owlish :valentin who helped reviewing bug 159133 for suggestions. I am happy to submit patches if there is a way to make the setting persistence without rolling back. Please let me know if I can help.

I'll confirm this bug, since I was able to reproduce it on the today's Nightly 119.0a1 build with Google Pixel 6 (Android 14).

Severity: -- → S3
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [qa-triaged]

Set release status flags based on info from the regressing bug 1591533

Adding needinfos re: comment 5

Flags: needinfo?(valentin.gosu)
Flags: needinfo?(bugzeeeeee)

I think we should backout bug 1591533 from Nightly and land it at a later point when we fix the GV API overwriting them. I suspect the number of users who use TRR on release is quite low, but we still should avoid changing their prefs.

Flags: needinfo?(valentin.gosu)

(In reply to Valentin Gosu [:valentin] (he/him) from comment #9)

I think we should backout bug 1591533 from Nightly and land it at a later point when we fix the GV API overwriting them. I suspect the number of users who use TRR on release is quite low, but we still should avoid changing their prefs.

I'll request the Sheriffs to backout

Flags: needinfo?(bugzeeeeee)
Summary: trr.mode after saturday nighlty reset at every app restart → trr.mode pref set via about:config resets when the browser is restarted

I've updated the summary to hopefully be a bit clearer about the specific issue.

(In reply to Valentin Gosu [:valentin] (he/him) from comment #9)

I think we should backout bug 1591533 from Nightly and land it at a later point when we fix the GV API overwriting them. I suspect the number of users who use TRR on release is quite low, but we still should avoid changing their prefs.

Unfortunately, it doesn't blackout cleanly from central due to Bug 1852804 which also touches changelog.md.
Could you please provide a patch that backs out cleanly?

Flags: needinfo?(valentin.gosu)
Flags: needinfo?(elizabbennet)
Assignee: nobody → valentin.gosu
Status: NEW → ASSIGNED
Flags: needinfo?(valentin.gosu)
Flags: needinfo?(elizabbennet)
Pushed by valentin.gosu@gmail.com: https://hg.mozilla.org/integration/autoland/rev/301cd75007d9 Backed out changeset f5d973fcd59c (bug 1591533) for resetting the TRR mode when set via about:config r=owlish

Set release status flags based on info from the regressing bug 1591533

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 120 Branch

The patch landed in nightly and beta is affected.
:valentin, is this bug important enough to require an uplift?

  • If yes, please nominate the patch for beta approval.
  • If no, please set status-firefox119 to wontfix.

For more information, please visit BugBot documentation.

Flags: needinfo?(valentin.gosu)

Comment on attachment 9354853 [details]
Bug 1854216 - Backed out changeset f5d973fcd59c (bug 1591533) for resetting the TRR mode when set via about:config r=owlish

Beta/Release Uplift Approval Request

  • User impact if declined: The network.trr.mode pref set by the user in about:config gets reset by GV API.
  • Is this code covered by automated tests?: Unknown
  • Has the fix been verified in Nightly?: No
  • Needs manual test from QE?: Yes
  • If yes, steps to reproduce: Set network.trr.mode to 3 in about:config, close Fenix, open it again, check that the pref is still set
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): Just a backout reverting to previous behaviour.
  • String changes made/needed:
  • Is Android affected?: Yes
Flags: needinfo?(valentin.gosu)
Attachment #9354853 - Flags: approval-mozilla-beta?
Flags: qe-verify+

Verified as fixed on the latest Fenix Nightly 120.0a1 from 9/28 with Google Pixel 6 (Android 14).

Status: RESOLVED → VERIFIED
Flags: qe-verify+

Comment on attachment 9354853 [details]
Bug 1854216 - Backed out changeset f5d973fcd59c (bug 1591533) for resetting the TRR mode when set via about:config r=owlish

Approved for 119.0b3

Attachment #9354853 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

Verified fixed on Beta 119.0b3 with Samsung Galaxy A53 5G (Android 13). The network.trr.mode param is no longer reset after restarting Fenix.

See Also: → 1865010
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: