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

Issue 644253 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug
Team-Security-UX



Sign in to add a comment

Move Navigation.MainFrameSchemeDifferentPage* metrics into a page load metric

Project Member Reported by f...@chromium.org, Sep 6 2016

Issue description

Page load metrics are the wave of the future. Move the HTTPS stat metrics there.

* Page load metrics code is set up to intentionally support this kind of use case
* Page load metrics explicitly ignore NTP URLs, 4xx pages, and non-HTML pages, which we really don't want to include
* Migrating will help PlzNavigate by removing the navigation callback
 
Cc: bmcquade@chromium.org csharrison@chromium.org
Components: -Security>UX Internals>PageSecurityState
Components: Internals>Permissions>CrowdConsent
Components: -Internals>Permissions>CrowdConsent

Comment 5 by est...@chromium.org, Nov 10 2017

Labels: Hotlist-EnamelAndFriendsFixIt

Comment 6 by est...@chromium.org, Feb 18 2018

Labels: -Hotlist-EnamelAndFriendsFixIt
Owner: cthomp@chromium.org
Hey Chris, sharing this with you in case you're interested in taking this on at some point. 
I'm not sure we want to do this. Navigation.MainFrameSchemeDifferentPage is a useful signal to have as a lower-level navigation metric that doesn't do any sort of filtering. Maybe it would be useful to have a variant logged for the same subset of pages PageLoadMetrics tracks, but I don't think we want to give it up completely.

The pro that migrating will help PlzNavigate is moot at this point anyway.

Sign in to add a comment