Two bit flags have same value in nsIClearDataService
Categories
(Toolkit :: Data Sanitization, defect, P1)
Tracking
()
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.
I can submit a quick patch for it although I'm still not sure how possible an automated test is.
Assignee | ||
Comment 1•9 months ago
|
||
Assignee | ||
Updated•9 months ago
|
Comment 2•9 months ago
|
||
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 :-)
Updated•9 months ago
|
Comment 3•9 months ago
|
||
Set release status flags based on info from the regressing bug 1782091
Updated•9 months ago
|
Assignee | ||
Updated•9 months ago
|
Assignee | ||
Updated•9 months ago
|
Comment 5•9 months ago
|
||
Please don't close bugs before they have landed. The sheriffs will close the bugs once the patch has landed.
Updated•9 months ago
|
Assignee | ||
Comment 6•9 months ago
|
||
My bad, thought status published == bug closed
Comment 7•9 months ago
•
|
||
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).
Comment 8•9 months ago
|
||
bugherder |
Comment 9•9 months ago
|
||
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
towontfix
.
For more information, please visit BugBot documentation.
Assignee | ||
Updated•9 months ago
|
Updated•9 months ago
|
Description
•