Plumb android intents into InputToFirstContentfulPaint metric |
||
Issue descriptionIn 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?
,
Oct 12
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..
,
Oct 12
,
Yesterday
(39 hours ago)
Still on Tom's plate. |
||
►
Sign in to add a comment |
||
Comment 1 by sullivan@chromium.org
, Oct 9