New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 739169 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Improve Normalization of Input Metrics

Project Member Reported by tdres...@chromium.org, Jul 4 2017

Issue description

Right now, all our input metrics are per input - i.e., per scroll, per scroll update, per key press, etc. Ideally we'd have some metrics that normalized these per page, or per touch sequence.

We should brainstorm on this at some point, but here are a few ideas:
- The worst scroll update per touch sequence.
- The worst scroll start per page view.
- The worst scroll update per page view.
- The worst key press per page view.
 
Status: Available (was: Untriaged)
Cc: bmcquade@chromium.org

Comment 3 by dproy@chromium.org, Mar 15 2018

Implementing worst input delay (Issue 822412) will be a step towards this direction. 

Comment 4 by npm@chromium.org, Jun 27 2018

Cc: dproy@chromium.org
dproy@ are you a good owner for this?
Status: WontFix (was: Available)
On second thought, I'm not sure what we do today is wrong.

WID is good, but is tracked separately.
I think we can probably just mark this obsolete.

Sign in to add a comment