Bug 1347507
(post-57-api-changes)
Stuff we can remove when legacy extensions are no longer supported
NEW
Unassigned
Status
()
People
(Reporter: hsivonen, Unassigned)
Tracking
(Depends on: 30 bugs, Blocks: 3 bugs, {meta})
Firefox Tracking Flags
(Not tracked)
Details
(Whiteboard: [qf-])
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•2 years ago
|
||
Whiteboard: [qf]
|
||
Updated•2 years ago
|
||
|
|
||
Updated•2 years ago
|
||
Whiteboard: [qf] → [qf-]
|
||
Updated•2 years ago
|
||
Alias: post-57-api-changes
|
||
Comment 1•a year ago
|
||
Since most people are doing the dep backwards...
|
|
||
Updated•a year ago
|
||
|
||
Updated•a year ago
|
||
|
|
||
Updated•a year ago
|
||
Depends on: 1385444
| Comment hidden (abuse-reviewed) |
|
||
Updated•a year ago
|
||
See Also: → bug 1388325
|
||
Updated•a year ago
|
||
|
||
Updated•10 months ago
|
||
Summary: Stuff we can remove when XPCOM extensions are no longer supported → Stuff we can remove when legacy extensions are no longer supported
You need to log in
before you can comment on or make changes to this bug.
Description
•