Closed
Bug 1947594
Opened 1 year ago
Closed 11 months ago
Remove nsChannelClassifier::SetBlockedContent
Categories
(Core :: Networking, task, P2)
Core
Networking
Tracking
()
RESOLVED
FIXED
138 Branch
| Tracking | Status | |
|---|---|---|
| firefox138 | --- | fixed |
People
(Reporter: edgul, Assigned: thampan)
Details
(Keywords: good-first-bug, Whiteboard: [necko-triaged])
Attachments
(1 file)
nsChannelClassifier::SetBlockedContent is neither defined, nor used (?).
https://searchfox.org/mozilla-central/rev/f89fa2093be1cedd708fb8c5538df98ba73f4456/netwerk/url-classifier/nsChannelClassifier.h#59-64
Let's remove it.
NI'ing anti-tracking team for sanity check. I'm not missing anything, right?
Severity: -- → N/A
Flags: needinfo?(tihuang)
Keywords: good-first-bug
Priority: -- → P2
Whiteboard: [necko-triaged]
|
||
Comment 2•1 year ago
|
||
I think we can remove the nsChannelClassifier::SetBlockedContent(). The functionality was moved to UrlClassifierCommon::SetBlockedContent()
Flags: needinfo?(tihuang)
|
||
Updated•11 months ago
|
Assignee: nobody → jishnu.mt
|
Assignee | |
Comment 3•11 months ago
|
||
Pushed by valentin.gosu@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/eb13318073d0
Remove unused nsChannelClassifier::SetBlockedContent. r=necko-reviewers,valentin
|
||
Comment 5•11 months ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 11 months ago
status-firefox138:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 138 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•