New issue
Advanced search Search tips

Issue 625699 link

Starred by 4 users

Issue metadata

Status: Archived
Owner:
Closed: Oct 9
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Feature



Sign in to add a comment

Input Latency - Progressive Web Metric

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

Issue description

Add Input Latency Progressive Web Metric.

Some discussion here:
https://docs.google.com/document/d/11aFLCWTgfLgbi_5cJT4pejzklRmgWYRGpXOgPO5xH-k/edit
 
Labels: Hotlist-Input-Dev
Components: -Metrics Internals>Metrics
Is this something we are committed to fix this quarter? ie; P1 is current milestone.
Labels: -Pri-1 Pri-2
Completing this is actually pretty ill defined. Bumping down to P2.
Components: Speed>Metrics
Components: -Internals>Metrics
There's still work to do here, though we're making slow progress.

Comment 8 by npm@chromium.org, Jan 12 2018

Any update on progress so far?
A somewhat outdated proposal can be found here:
https://docs.google.com/document/d/1_jKAyTvMN2xEDmqttozWDIWGfhSwecaDrkHZ0dWkOns/edit#heading=h.dwvjsxc3b2d2

We should have an updated explainer out by EOQ.

Comment 10 by dproy@chromium.org, Mar 16 2018

Labels: -progressivewebmetrics

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

Tim, this looks like it can be marked as duplicate of issue 841224, right?
This was also intended to cover a Chrome input latency metric, which that doesn't.

I'll leave this open to track that work.
Status: Archived (was: Assigned)
This work is tracked elsewhere.

Sign in to add a comment