1490074 - Add Telemetry to know how long the AudioContext become audible since it was created

Status: RESOLVED FIXED

(Core :: Audio/Video: Playback, enhancement, P2)

Description

[Alastor Wu [:alwu]]

> padenot : creating an AudioContext when you don't want to play is very bad, it wake up the audio hardware of your phone, pauses your music, and consumes CPU for nothing

Although we know that sites shouldn't create AudioContext in advance, it wastes the resource a lot and also causes the doorhanger showing too early even there is no any audible autoplay.

I don't like to show the doorhanger when there is no audible autoplay, I would like to keep the timing of showing the doorhanger as close as possible to the timing audible autoplay happens. 

Therefore , I want to know how many sites will have that scenario which is to create AudioContext in advance and produces sound later (ex. when user click the page or certain button).

I will add a Telemetry probe to meausure how long the AudioContext would become audible since it was created.

Comment 1

[Alastor Wu [:alwu]]

Attachment: Bug 1490074 - add Telemetry to know how long the AudioContext become audible since it was created.

I want to know how many sites will have that scenario which is to create AudioContext in advance and produces sound later (ex. when user click the page or certain button).

I will add a Telemetry probe to meausure how long the AudioContext would become audible since it was created.

Comment 2

[Alastor Wu [:alwu]]

Attachment: Data review request

Comment 3

[François Marier [:francois]]

Comment on attachment 9007859 [details]
Data review request

1) Is there or will there be **documentation** that describes the schema for the ultimate data set available publicly, complete and accurate?

Yes, in Histograms.json.

2) Is there a control mechanism that allows the user to turn the data collection on and off?

Yes, telemetry setting.

3) If the request is for permanent data collection, is there someone who will monitor the data over time?**

Not permanent.

4) Using the **[category system of data types](https://wiki.mozilla.org/Firefox/Data_Collection)** on the Mozilla wiki, what collection type of data do the requested measurements fall under?  **

Category 1.

5) Is the data collection request for default-on or default-off?

Default ON, all channels.

6) Does the instrumentation include the addition of **any *new* identifiers** (whether anonymous or otherwise; e.g., username, random IDs, etc.  See the appendix for more details)?

No.

7) Is the data collection covered by the existing Firefox privacy notice?

Yes.

8) Does there need to be a check-in in the future to determine whether to renew the data?

No, telemetry alerts are sufficient.

Comment 4

[François Marier [:francois]]

Comment on attachment 9007856 [details]
Bug 1490074 - add Telemetry to know how long the AudioContext become audible since it was created.

François Marier [:francois] has approved the revision.

Comment 5

[Paul Adenot (:padenot)]

Comment on attachment 9007856 [details]
Bug 1490074 - add Telemetry to know how long the AudioContext become audible since it was created.

Paul Adenot (:padenot) has approved the revision.

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/84fbf23400d5
add Telemetry to know how long the AudioContext become audible since it was created. r=padenot,francois

Comment 7

[Noemi Erli[:noemi_erli]]

https://hg.mozilla.org/mozilla-central/rev/84fbf23400d5