Closed Bug 2022643 Opened 2 months ago Closed 2 months ago

Allow UTF-8 BOM at the beginning of a pref file

Categories

(Core :: Preferences: Backend, defect)

defect

Tracking

()

RESOLVED FIXED
150 Branch
Tracking Status
firefox-esr140 --- fixed
firefox149 --- fixed
firefox150 --- fixed

People

(Reporter: gstoll, Assigned: gstoll)

References

Details

Attachments

(3 files)

The telemetry data we gathered in bug 2004956 indicates that users have prefs files with a UTF-8 BOM that the prefs parser does not handle correctly. We can just skip over these bytes and parse the file as normal (in our sample data, all of the files would have parsed correctly if we had done this)

Assignee: nobody → gstoll
Status: NEW → ASSIGNED

Our telemetry data indicates that this is pretty common. (in an admittedly
small sample) I will continue monitoring the failure rate after this goes
in to see if we get any improvements in Nightly.

Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 150 Branch

firefox-beta Uplift Approval Request

  • User impact if declined/Reason for urgency: simple fix that could significantly reduce the number of users for which we fail to parse prefs files (fingers crossed!)
  • Code covered by automated testing?: yes
  • Fix verified in Nightly?: no
  • Needs manual QE testing?: no
  • Steps to reproduce for manual QE testing: n/a
  • Risk associated with taking this patch: low
  • Explanation of risk level: just skip a few bytes at the beginning of a prefs file if it's a UTF8 BOM
  • String changes made/needed?: no
  • Is Android affected?: yes
Attachment #9552652 - Flags: approval-mozilla-beta?

Our telemetry data indicates that this is pretty common. (in an admittedly
small sample) I will continue monitoring the failure rate after this goes
in to see if we get any improvements in Nightly.

Original Revision: https://phabricator.services.mozilla.com/D287210

firefox-esr140 Uplift Approval Request

  • User impact if declined/Reason for urgency: simple fix that could significantly reduce the number of users for which we fail to parse prefs files (fingers crossed!)
  • Code covered by automated testing?: yes
  • Fix verified in Nightly?: no
  • Needs manual QE testing?: no
  • Steps to reproduce for manual QE testing: n/a
  • Risk associated with taking this patch: low
  • Explanation of risk level: just skip a few bytes at the beginning of a prefs file if it's a UTF8 BOM
  • String changes made/needed?: no
  • Is Android affected?: yes
Attachment #9552653 - Flags: approval-mozilla-esr140?

Our telemetry data indicates that this is pretty common. (in an admittedly
small sample) I will continue monitoring the failure rate after this goes
in to see if we get any improvements in Nightly.

Original Revision: https://phabricator.services.mozilla.com/D287210

Attachment #9552652 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Attachment #9552653 - Flags: approval-mozilla-esr140? → approval-mozilla-esr140+
QA Whiteboard: [qa-triage-done-c150/b149]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: