Open
Bug 1347507
(post-57-api-changes)
Opened 7 years ago
Updated 9 months ago
[meta] Stuff we can remove when legacy extensions are no longer supported
Categories
(Core :: XPCOM, enhancement)
Core
XPCOM
Tracking
()
NEW
Performance Impact | none |
People
(Reporter: hsivonen, Unassigned)
References
(Depends on 17 open bugs, Blocks 3 open bugs)
Details
(Keywords: meta)
This is a tracking bug for stuff we can remove once XPCOM extensions are no longer supported. Bugs for removals of things that are obsoleted by the removal of XPCOM extensions can depend on this bug.
Updated•7 years ago
|
Blocks: OMT-nsIURI
Updated•7 years ago
|
Whiteboard: [qf]
Updated•7 years ago
|
Updated•7 years ago
|
Whiteboard: [qf] → [qf-]
Updated•6 years ago
|
Alias: post-57-api-changes
![]() |
||
Comment 1•6 years ago
|
||
Since most people are doing the dep backwards...
![]() |
||
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Comment hidden (abuse-reviewed) |
Updated•6 years ago
|
Updated•6 years ago
|
Depends on: war-on-xbl
Updated•6 years ago
|
Summary: Stuff we can remove when XPCOM extensions are no longer supported → Stuff we can remove when legacy extensions are no longer supported
Updated•5 years ago
|
Summary: Stuff we can remove when legacy extensions are no longer supported → [meta] Stuff we can remove when legacy extensions are no longer supported
Updated•2 years ago
|
Performance Impact: --- → -
Whiteboard: [qf-]
Updated•1 year ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•