Closed Bug 1899319 Opened 9 months ago Closed 9 months ago

Two bit flags have same value in nsIClearDataService

Categories

(Toolkit :: Data Sanitization, defect, P1)

defect

Tracking

()

RESOLVED FIXED
128 Branch
Tracking Status
firefox-esr115 --- wontfix
firefox126 --- wontfix
firefox127 --- wontfix
firefox128 --- fixed

People

(Reporter: wwen, Assigned: wwen)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

Two flags used to clear data in the nsIClearDataService have the same value.

https://searchfox.org/mozilla-central/source/toolkit/components/cleardata/nsIClearDataService.idl#280-288

I can submit a quick patch for it although I'm still not sure how possible an automated test is.

Severity: -- → S3
Priority: -- → P2

Well spotted! Thanks for submitting a patch too.

(In reply to William Wen (:wwen) from comment #0)

I can submit a quick patch for it although I'm still not sure how possible an automated test is.

I think adding something based on what we discussed would be good:

Object.keys(Ci.nsIClearDataService).filter(k => k.startsWith("CLEAR_"))

Unfortunately my browser console currently doesn't work so I can't test this myself. You might have to manually exclude certain group flags along with the CLEAR_ALL one. but it's better than nothing :-)

Component: Sanitizers → Data Sanitization
Priority: P2 → P1
Product: Core → Toolkit

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

Status: NEW → ASSIGNED
Pushed by pzuhlcke@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/86c93771026b Change bit flags to not have duplicate values. r=bvandersloot,pbz
Status: ASSIGNED → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED

Please don't close bugs before they have landed. The sheriffs will close the bugs once the patch has landed.

Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → ASSIGNED

My bad, thought status published == bug closed

Expanding on comment 5: the bug's not considered fixed until the patch merges to mozilla-central, since that's what Nightly is built from (and what ultimately merges to beta, etc).

The phabricator "published" status just means that it landed on autoland (e.g. comment 4); but often a half-day or so can go by between merges from autoland to mozilla-central (or more, in rare cases where there's substantial bustange on autoland that needs cleaning up, or other infrastructure issues).

Status: ASSIGNED → RESOLVED
Closed: 9 months ago9 months ago
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch

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

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

For more information, please visit BugBot documentation.

Flags: needinfo?(wwen)
Flags: needinfo?(wwen)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: