Closed
Bug 1107782
Opened 8 years ago
Closed 7 years ago
Fix EventStateManagers event filter for "user-interaction-active"
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Tracking
()
RESOLVED
FIXED
mozilla45
Tracking | Status | |
---|---|---|
firefox45 | --- | fixed |
People
(Reporter: gfritzsche, Assigned: chutten)
References
Details
Attachments
(1 file, 3 obsolete files)
2.35 KB,
patch
|
chutten
:
review+
|
Details | Diff | Splinter Review |
Currently we count NS_MOUSE_MOZHITTEST for "user-interaction-active", which is wrong.
Comment 1•8 years ago
|
||
blacklist might be just fine here too, but sure NS_MOUSE_MOZHITTEST isn't a user input. Want to write a patch? I promise a fast review :)
Reporter | ||
Comment 2•8 years ago
|
||
I will put a patch up, was just too tired earlier. Whitelisting sounds more robust in case of new event types being added (most likely they are not tracked activity).
Comment 3•8 years ago
|
||
We should be aware that fixing this bug could have some implications, including possibly lower number of FHR activeTicks count, more opportunities for maintenance tasks (GC/CC etc) etc.
Comment 4•8 years ago
|
||
We don't use user-interaction-* for GC/CC scheduling anymore.
Reporter | ||
Comment 5•8 years ago
|
||
This fixes the mouse filtering. Looking through the events we have, we were definitely missing gamepad events, i added those. What i'm not sure about yet is whether we account for touch events properly (surface devices & other touchscreens). Not asking for review at this point because our important activeTicks metric is based on this and we have to figure out whether we can break it.
Reporter | ||
Updated•8 years ago
|
Summary: EventStateManager should whitelist mouse events for "user-interaction-active" → Fix EventStateManagers event filter for "user-interaction-active"
Reporter | ||
Comment 6•8 years ago
|
||
bsmedberg, i believe there are talks ongoing on whether we can change this, which implies changing the activeTicks metrics significantly. Were there any results on that yet?
Flags: needinfo?(benjamin)
Comment 7•8 years ago
|
||
Personally I'd prefer we add a "user-interaction-active2" event and report it in a new field. It looks like it wouldn't be too hard to do based on this patch. I defer the decision to Benjamin, he knows better how the Firefox usage metric is actually used
Comment 8•8 years ago
|
||
(In reply to Vladan Djeric (:vladan) from comment #7) > Personally I'd prefer we add a "user-interaction-active2" event Please no. That would just cause confusion. We don't really use user-interaction-* in Gecko atm. The notification is used only by services/datareporting/sessions.jsm so I'm sure it could be tweaked to deal with the possible change in notification triggering. (There have be several changes to how we trigger the user-interaction-* notifications in the past.)
Reporter | ||
Comment 9•8 years ago
|
||
(In reply to Olli Pettay [:smaug] from comment #8) > The notification is used only by services/datareporting/sessions.jsm so I'm > sure it could be tweaked to deal with the possible change in notification > triggering. If it suddenly just triggers differently, i don't think we can keep the metric based on it stable. I think it really comes down whether we can live with changing the context for the metric while we're fixing things.
Comment 10•8 years ago
|
||
Just a reminder since I don't see it mentioned explicitly: if you change the behavior of the event, you should bump the FHR measurement version. That way server-side analysis will be able to easily differentiate between the 2 population sets.
Reporter | ||
Comment 11•8 years ago
|
||
The issue we need a decision on is with losing the historic basis for comparison on this metric.
Reporter | ||
Comment 12•8 years ago
|
||
So we are currently ok with changes to this metric, provided they go with a bump to the FHR provider version.
Flags: needinfo?(benjamin)
Reporter | ||
Comment 13•8 years ago
|
||
Comment on attachment 8532727 [details] [diff] [review] Fix event filter for "user-interaction-active"/"-inactive" smaug, does this good? Do you think this is complete regarding events that represent user activity? What about touch events or other things?
Attachment #8532727 -
Flags: review?(bugs)
Comment 14•8 years ago
|
||
Comment on attachment 8532727 [details] [diff] [review] Fix event filter for "user-interaction-active"/"-inactive" For touch, just add aEvent->mClass == eTouchEventClass
Attachment #8532727 -
Flags: review?(bugs) → review+
Reporter | ||
Comment 15•8 years ago
|
||
Updated to review comment.
Attachment #8532727 -
Attachment is obsolete: true
Attachment #8536654 -
Flags: review+
Comment 16•8 years ago
|
||
Please hold off on landing this until I hear back form the FHR people. I think code ugliness (two user-interaction-active notifications & two activeTicks counts) for a release or two is bearable if it helps maintain continuity of an important metric like usage hours
Reporter | ||
Updated•8 years ago
|
Reporter | ||
Comment 17•8 years ago
|
||
I don't actually have time for this right now with the FHR/Telemetry unification work.
Assignee: gfritzsche → nobody
![]() |
||
Updated•8 years ago
|
Updated•8 years ago
|
Assignee: nobody → chutten
Assignee | ||
Comment 18•7 years ago
|
||
On Windows we're sending artificial hittests every 200ms if there's a mouse just hanging idle over one of our windows. bug 506815 is where I'm looking to stop that. Even without :gfritzsche's patch that'll make quite the change to the existing measurement. There's coordination needed here.
Assignee | ||
Comment 19•7 years ago
|
||
From discussion on fhr-dev ( https://mail.mozilla.org/pipermail/fhr-dev/2015-November/000688.html ) we're good to get this patch in. Here's the trypush: https://treeherder.mozilla.org/#/jobs?repo=try&revision=e83d9a37db63 Since the first patch, touch events were added and events' messages became an enum mMessage. Otherwise, the patch is mostly untouched.
Attachment #8536654 -
Attachment is obsolete: true
Attachment #8691009 -
Flags: review?(gfritzsche)
Reporter | ||
Comment 20•7 years ago
|
||
Comment on attachment 8691009 [details] [diff] [review] 0001-bug-1107782-Only-accept-certain-mouse-gamepad-events.patch Great to see this finally landing. Moving the review to smaug who actually knows about this code.
Attachment #8691009 -
Flags: review?(gfritzsche) → review?(bugs)
Reporter | ||
Updated•7 years ago
|
Status: NEW → ASSIGNED
Comment 21•7 years ago
|
||
Comment on attachment 8691009 [details] [diff] [review] 0001-bug-1107782-Only-accept-certain-mouse-gamepad-events.patch >+static bool >+IsMessageMouseUserActivity(EventMessage m) Nit, argument names should be in form aName, so aMessage here >+static bool >+IsMessageGamepadUserActivity(EventMessage m) ditto
Attachment #8691009 -
Flags: review?(bugs) → review+
Assignee | ||
Comment 22•7 years ago
|
||
Attachment #8691009 -
Attachment is obsolete: true
Attachment #8691363 -
Flags: review+
Assignee | ||
Updated•7 years ago
|
Keywords: checkin-needed
Comment 23•7 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/e7a5e293d017
Keywords: checkin-needed
Comment 24•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/e7a5e293d017
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox45:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla45
Updated•4 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•