Closed
Bug 902075
Opened 11 years ago
Closed 11 years ago
Add telemetry for usage patterns of click-to-play plugins
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla26
People
(Reporter: benjamin, Assigned: benjamin)
References
Details
Attachments
(1 file, 1 obsolete file)
As we turn click-to-play on by default for most plugins, I want telemetry data indicating how people actually use the UI: * clicks on in-content UI * clicks on doorhanger icon * single versus multi-plugin UI * click rates for allowonce/allowalways/stop allowing
Updated•11 years ago
|
Assignee | ||
Comment 1•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Attachment #796831 -
Flags: review?(vdjeric)
Comment 2•11 years ago
|
||
Comment on attachment 796831 [details] [diff] [review] Add telemetry for plugin click-to-activate doorhanger UI, r?vladan >+ // Histograms always start at 0, even though our data starts at 1 >+ var histogramCount = centerActions.length - 1; - Frontend code uses "let" now afaik - Is it possible for centerActions.length to be zero?
Attachment #796831 -
Flags: review?(vdjeric) → review+
Assignee | ||
Comment 3•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Attachment #796831 -
Attachment is obsolete: true
Comment 5•11 years ago
|
||
Given the "CtP discoverability issues" discussion on firefox-dev, should/can we extend this to get data on "hidden" vs. "non hidden" plugin volumes?
Updated•11 years ago
|
Flags: needinfo?(benjamin)
Comment 6•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/1e63861a73d9
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla26
Assignee | ||
Comment 7•11 years ago
|
||
Currently this doesn't have any telemetry for when we show the icon, only when the user clicks it. That's partly because we recreate the doorhanger/icon fairly often. Any extension of the data should of course be in another bug.
Flags: needinfo?(benjamin)
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•