Closed Bug 855945 Opened 9 years ago Closed 4 years ago
Add telemetry probe for type of pointer / keyboard input
See bug 828562 comment 0. We would like to track the types of input devices that users are using in Firefox immersive/Metro. One way we can approach this is to have probes that keep track of when "mousedown, mouseup, touchstart, touchend, keydown, and keyup" are generated from physical input. We'll want the probes to differentiate between physical keyboard and soft keyboard (is this possible?), and between mouse, pen, and touch.
Whiteboard: feature=story c=data_submission u=metro_firefox_user p=13 → feature=story c=data_submission u=metro_firefox_user p=1
Jim do you know what we need to do to detect this? (Given the p=1 change)
(In reply to Brian R. Bondy [:bbondy] from comment #1) > Jim do you know what we need to do to detect this? (Given the p=1 change) I think what we want is three flags, touch, mouse, pen, set over some time period (last week, or day or something?). Not sure about the keyboard flag, seems like what we are most interested in is touch vs. mouse.
(For detection/location we can do this in the front end using event source info or down in widget.)
So jimm noted in irc today that telling the hardware keyboards from the software keyboards will need to be deep in widget, which will make this a multi-part project and possibly not worth the effort for v1. Also we need to figure out exactly what we want to gather before we can go about implementing it
Assignee: ally → nobody
Summary: Story - Add telemetry probe for input → Add telemetry probe for input
Whiteboard: feature=story c=data_submission u=metro_firefox_user p=0 → [story]
Summary: Add telemetry probe for input → Add telemetry probe for type of pointer / keyboard input
Component: Metro Operations → General
Product: Tracking → Firefox for Metro
Version: --- → Trunk
OS: Windows 8 Metro → Windows 8.1
Mass close of bugs in obsolete product https://bugzilla.mozilla.org/show_bug.cgi?id=1350354
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.