Closed
Bug 1728760
Opened 4 years ago
Closed 4 years ago
Make all native nsITimerCallback implementations also implement nsINamed
Categories
(Core :: XPCOM, task)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
94 Branch
Tracking | Status | |
---|---|---|
firefox94 | --- | fixed |
People
(Reporter: florian, Assigned: florian)
References
Details
Attachments
(2 files)
Bug 1382172 did this 4 years ago, and we now have many new nsITimerCallback implementations that don't implement nsINamed. It would be nice to ensure at compile time that all native nsITimerCallback implementations also implement nsINamed.
These names are exposed in profiler markers (from bug 1688300 and bug 1728228).
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Comment 2•4 years ago
|
||
Pushed by fqueze@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/79474e4c8adf
require all nsITimerCallback native implementations to also implement nsINamed, r=smaug.
https://hg.mozilla.org/integration/autoland/rev/5710a72e4438
move the nsHttpChannel nsITimerCallback implementation to a nested subclass to avoid issues when an object implements both nsIChannel and nsIRequest, r=smaug,necko-reviewers,kershaw.
Comment 4•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/79474e4c8adf
https://hg.mozilla.org/mozilla-central/rev/5710a72e4438
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox94:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 94 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•