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

Issue 893162 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug

Blocking:
issue 889220



Sign in to add a comment

Plumb android intents into InputToFirstContentfulPaint metric

Project Member Reported by sullivan@chromium.org, Oct 8

Issue description

In bug 889220, we're working on making InputToFirstContentfulPaint have coverage for all page loads where there is user input. One thing uncovered in the analysis is that the metric currently doesn't include user inputs from Android intents, and it should.

LoadURLParams already has a mIntentReceivedTimestamp: https://cs.chromium.org/chromium/src/content/public/android/java/src/org/chromium/content_public/browser/LoadUrlParams.java?q=intentreceivedtimestamp&sq=package:chromium&dr=CSs&l=43

This is the time the intent was received, not the time of the user input. Not sure if it's possible to get the latter; if not, perhaps the former is the best we can do?
 
Owner: tommckee@chromium.org
Note: while working on this, we should manually test that pages loaded in the foreground through intents are actually counted properly in CorePageLoadMetricsObserver. It's possible that when creating the WebContents, we look at the foreground/background status too early and count them as background loads..
Status: Assigned (was: Untriaged)

Comment 4 by tdres...@chromium.org, Yesterday (39 hours ago)

Still on Tom's plate.

Sign in to add a comment