Closed
Bug 1358345
Opened 7 years ago
Closed 9 months ago
dom/security/nsContentSecurityManager.cpp has two #include "nsIStreamListener.h"
Categories
(Core :: DOM: Security, enhancement, P3)
Core
DOM: Security
Tracking
()
RESOLVED
DUPLICATE
of bug 1754767
People
(Reporter: ewong, Unassigned)
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file)
line #4 and line #8 contains #include "nsIStreamListener.h". according to :jdm on irc, it's not necessary. filing this bug.
Comment hidden (mozreview-request) |
Reporter | ||
Updated•7 years ago
|
Assignee: nobody → ewong
Status: NEW → ASSIGNED
Flags: needinfo?(bzbarsky)
Reporter | ||
Updated•7 years ago
|
Flags: needinfo?(bzbarsky)
Comment 2•7 years ago
|
||
mozreview-review |
Comment on attachment 8860260 [details] Bug 1358345 - Remove extra instance of #include 'nsIStreamListener.h' https://reviewboard.mozilla.org/r/132274/#review135186 Thanks - please update the commit message though!
Attachment #8860260 -
Flags: review+
Updated•7 years ago
|
Priority: -- → P2
Whiteboard: [domsecurity-active]
Reporter | ||
Comment 3•7 years ago
|
||
mozreview-review-reply |
Comment on attachment 8860260 [details] Bug 1358345 - Remove extra instance of #include 'nsIStreamListener.h' https://reviewboard.mozilla.org/r/132274/#review135186 pardon my ignorance, but what's the mozreview way of updating the commit message? (more so, what exactly do I update it to?)
Comment 4•7 years ago
|
||
I am not really using mozreview, but I would imagine it's the same as a regular commit message: hg qrefresh -m "Bug 1358345 - Remove extra instance of #include 'nsIStreamListener.h'. r=ckerschb"
Comment hidden (mozreview-request) |
Comment 6•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Comment 7•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: ewong → nobody
Status: ASSIGNED → NEW
Updated•2 years ago
|
Severity: normal → S3
Reporter | ||
Comment 8•9 months ago
|
||
I don't even think this is even applicable anymore. Was fixed in bug 1754767.
You need to log in
before you can comment on or make changes to this bug.
Description
•