Add a Telemetry to know how many users are blocking muted media by default
Categories
(Core :: Audio/Video: Playback, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox70 | --- | fixed |
People
(Reporter: alwu, Assigned: alwu)
References
Details
Attachments
(2 files, 4 obsolete files)
47 bytes,
text/x-phabricator-request
|
Details | Review | |
1.79 KB,
text/plain
|
tdsmith
:
data-review+
|
Details |
We should extend the Telemetry ping media.autoplay_default_blocked
[1] or have a new one to record the amount of blocking muted media by default.
Assignee | ||
Comment 1•5 years ago
|
||
Bug 1356046 incorrectly removed the current ping media.autoplay_default_blocked
.
Assignee | ||
Comment 2•5 years ago
|
||
As this scalar was incorrectly removed in bug1356046, which should only remove expired Telemetry, we revert the change.
Assignee | ||
Comment 3•5 years ago
|
||
As we have extended the pref media.autoplay_default_blocked
in bug1543812, we also want to know how many users choose to block all media, not just blocking audible media.
Therefore, change this scalar to uint
to accept new value, and modify the release collection option because we would like to know how users in release channel would use this feature.
Assignee | ||
Comment 4•5 years ago
|
||
Assignee | ||
Comment 5•5 years ago
|
||
Comment on attachment 9083450 [details]
Data review request
postpone the data review, because I'm thinking about maybe we should not use scalar for this one.
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 6•5 years ago
|
||
We acutally have an old Telemetry ping autoplay_default_blocked
, which, however, has been removed incorrectly in bug1356046.
As we have extended the setting options of blocking autoplay in bug1543812, it's also no longer proper to use scalar to store it.
Therefore, create an new histogram Telemetry ping to store the amount of the value of different autoplay setting option.
(0=allow, 1=block audible, 5=block all, they are from the pref 'media.autoplay.default')
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 7•5 years ago
|
||
Comment 8•5 years ago
|
||
Comment on attachment 9083486 [details]
Data review request
Load balancing to :tdsmith.
Comment 9•5 years ago
|
||
Comment on attachment 9083486 [details]
Data review request
Please flag me for data-review again once the documentation is updated.
1) Is there or will there be **documentation** that describes the schema for the ultimate data set in a public, complete, and accurate way?
No; the documentation in the current patch revision does not seem to match the behavior of the probe, and the measurement population in the request and the patch are different.
Assignee | ||
Comment 10•5 years ago
|
||
Comment 11•5 years ago
|
||
Comment on attachment 9084094 [details] Data review request 1) Is there or will there be **documentation** that describes the schema for the ultimate data set in a public, complete, and accurate way? Yes, Histograms.json and the probe dictionary. 2) Is there a control mechanism that allows the user to turn the data collection on and off? Yes, the Firefox telemetry opt-out. 3) If the request is for permanent data collection, is there someone who will monitor the data over time? n/a 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 2, interaction data. 5) Is the data collection request for default-on or default-off? Default-on. 6) Does the instrumentation include the addition of **any *new* identifiers**? 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? (Yes/No) Yes; alwu is responsible for deciding whether to renew the probe before it expires. 9) Does the data collection use a third-party collection tool? No.
Comment 12•5 years ago
|
||
Pushed by alwu@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ad2abcfa0875 add a Telemetry ping to record the deault setting of blocking autoplay. r=janerik,daleharvey
Comment 13•5 years ago
|
||
bugherder |
Description
•