Closed
Bug 855945
Opened 11 years ago
Closed 7 years ago
Add telemetry probe for type of pointer / keyboard input
Categories
(Firefox for Metro Graveyard :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: TimAbraldes, Unassigned)
References
Details
(Whiteboard: p=2)
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.
Updated•11 years ago
|
Blocks: metrov1backlog
QA Contact: jbecerra
Updated•11 years ago
|
Priority: -- → P2
Updated•11 years ago
|
Priority: P2 → P4
Updated•11 years ago
|
Whiteboard: feature=story c=data_submission u=metro_firefox_user p=13 → feature=story c=data_submission u=metro_firefox_user p=1
Updated•11 years ago
|
Priority: P4 → P3
Comment 1•11 years ago
|
||
Jim do you know what we need to do to detect this? (Given the p=1 change)
Comment 2•11 years ago
|
||
(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.
Comment 3•11 years ago
|
||
(For detection/location we can do this in the front end using event source info or down in widget.)
Updated•11 years ago
|
Assignee: nobody → ally
Comment 4•11 years ago
|
||
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
Updated•11 years ago
|
Whiteboard: feature=story c=data_submission u=metro_firefox_user p=1 → feature=story c=data_submission u=metro_firefox_user p=0
Updated•11 years ago
|
Updated•11 years ago
|
Blocks: metrobacklog
Updated•11 years ago
|
No longer blocks: metrov2planning
Updated•11 years ago
|
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]
Updated•10 years ago
|
Summary: Add telemetry probe for input → Add telemetry probe for type of pointer / keyboard input
Updated•10 years ago
|
Whiteboard: [feature] p=0 → [feature] p=2
Updated•10 years ago
|
Priority: P3 → --
QA Contact: jbecerra
Updated•10 years ago
|
Priority: -- → P2
Updated•10 years ago
|
Component: Metro Operations → General
Product: Tracking → Firefox for Metro
Version: --- → Trunk
Updated•10 years ago
|
Whiteboard: [feature] p=2 → p=2
Assignee | ||
Updated•10 years ago
|
OS: Windows 8 Metro → Windows 8.1
Comment 5•7 years ago
|
||
Mass close of bugs in obsolete product https://bugzilla.mozilla.org/show_bug.cgi?id=1350354
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•