1387169 - Remove XPCOM interfaces that have WebIDL equivalents

Status: NEW

(Core :: DOM: Core & HTML, enhancement, P2)

Description

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

With the deprecation of XPCOM based extensions happens in Firefox 57, we can remove XPCOM components that have equivalent WebIDL interfaces/implementations.

This cleanup will happen in 2 steps, based on timing.

- During the period before 57 moves to beta, we can gut XPIDL interfaces, which will remove a good bit of code both generated and hand-written. This can be done as cleanup while working on other bugs that may touch code near the interfaces.
- After 57 moves to beta (2017-09-20 according to https://wiki.mozilla.org/RapidRelease/Calendar), we can be sure that no extensions will be using the interfaces, and can remove them completely from chrome js and kComponentsInterfaceShimMap.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Note: the things appearing in kInterfaceShimMap may need telemetry to remove, so we should think about adding such telemetry...

Comment 2

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

(In reply to Boris Zbarsky [:bz] from comment #1)
> Note: the things appearing in kInterfaceShimMap may need telemetry to
> remove, so we should think about adding such telemetry...

Filed as bug 1387178

Comment 3

[Masatoshi Kimura [:emk]]

(In reply to Kyle Machulis [:qdot] [:kmachulis]  (if a patch has no decent commit message, automatic r-) from comment #0)
> - After 57 moves to beta (2017-09-20 according to
> https://wiki.mozilla.org/RapidRelease/Calendar), we can be sure that no
> extensions will be using the interfaces, and can remove them completely from
> chrome js and kComponentsInterfaceShimMap.

Why do we have to wait until 57 moves to beta?

Comment 4

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

Gonna assume that dependency removal was accidental?

Comment 5

[Thomas Wisniewski]

Um, yes, sorry about that :S  I'm not sure how I managed to do that.