1134702 - TelemetryPing doesn't need to listen to app-startup and content-child-shutdown

Status: RESOLVED WORKSFORME

(Toolkit :: Telemetry, defect)

Description

[Georg Fritzsche [:gfritzsche]]

With breaking out things into TelemetrySession.jsm, TelemetryPing.jsm should only be used in the chrome process.
So:
* use a lazyModuleGetter for TelemetryPing.jsm in TelemetryStartup.js
* don't notify TelemetryPing of "app-startup" in TelemetryStartup.js
* remove "app-startup" and "content-child-shutdown" usage from TelemetryPing.observe

Comment 1

[Alessio Placitelli [:Dexter]]

I think this bug needs to be changed or resolved due to the changes in bug 1137252.

- TelemetryPing needs to use "app-startup" to initialize Telemetry.canRecord* in the content (it was done in TelemetrySession but bug 1137252 moved that to TelemetryPing, so that all the initialization happens in one place).
- TelemetryPing no longer uses content-child-shutdown (it was really just using that to call |Preferences.ignore(PREF_BRANCH_LOG, configureLogging);|, which was moved to TelemetryPing shutdown).

Comment 2

[Georg Fritzsche [:gfritzsche]]

This is obsoleted by the recent refactorings and other work.