Closed
Bug 2060649
Opened 3 days ago
Closed 2 days ago
Remove unused BounceTrackingState::ShouldCreateBounceTrackingStateForBC declaration
Categories
(Core :: Privacy: Anti-Tracking, task, P3)
Core
Privacy: Anti-Tracking
Tracking
()
RESOLVED
FIXED
155 Branch
| Tracking | Status | |
|---|---|---|
| firefox155 | --- | fixed |
People
(Reporter: emz, Assigned: nirmaladvani, Mentored)
References
(Blocks 1 open bug)
Details
(Keywords: good-first-bug, Whiteboard: [lang=C++])
Attachments
(1 file)
BounceTrackingState::ShouldCreateBounceTrackingStateForBC is declared in
toolkit/components/antitracking/bouncetrackingprotection/BounceTrackingState.h but has no definition anywhere in the tree and no callers. A tree-wide search for the identifier returns only that one declaration.
The sibling ShouldCreateBounceTrackingStateForWebProgress is the one actually used, and is declared and defined a few lines away.
Fix: delete the declaration.
Steps
- Search the tree for
ShouldCreateBounceTrackingStateForBCand confirm the single declaration is the only hit. - Delete those lines from
BounceTrackingState.h. - Build with
./mach buildand run./mach test --headless toolkit/components/antitracking/bouncetrackingprotection/testto confirm nothing regressed.
This is a good first bug: self-contained, no behaviour change, and the verification is a single search plus a build.
| Reporter | ||
Updated•3 days ago
|
Severity: -- → N/A
Priority: -- → P3
Whiteboard: [lang=C++]
| Reporter | ||
Updated•3 days ago
|
Mentor: emz
| Assignee | ||
Comment 1•3 days ago
|
||
Updated•3 days ago
|
Assignee: nobody → nirmaladvani
Status: NEW → ASSIGNED
Pushed by ezuehlcke@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/70483802e079
https://hg.mozilla.org/integration/autoland/rev/fe8a13040420
Remove unused BounceTrackingState::ShouldCreateBounceTrackingStateForBC declaration r=emz
Status: ASSIGNED → RESOLVED
Closed: 2 days ago
status-firefox155:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 155 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•