tools/metrics/histograms/histograms.xml - Issue 949323002: Collecting UMA metrics for the UnmaskPrompt.

Unified Diff: tools/metrics/histograms/histograms.xml

Side-by-side diff isn't available for this file because of its large size.

Issue 949323002: Collecting UMA metrics for the UnmaskPrompt. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Created 5 years, 9 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

Download patch

Index: tools/metrics/histograms/histograms.xml

diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml

index 0cb8649f23eea05b2aed352551d059f8eaa5ab2b..3fb6708d787b5ce6b23693ce0050a978f2f0f2a2 100644

--- a/tools/metrics/histograms/histograms.xml

+++ b/tools/metrics/histograms/histograms.xml

@@ -465,14 +465,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Apps.AppListDoodleAction" enum="AppListDoodleAction">

- <owner>calamity@chromium.org</owner>

- <summary>

- The number of user interactions with the app list doodle. This is logged

- once per action.

- </summary>

-</histogram>

<owner>tapted@chromium.org</owner>

@@ -483,14 +475,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Apps.AppListPageOpened" enum="AppListPage">

- <owner>calamity@chromium.org</owner>

- <summary>

- The page that the app list goes to. This is gathered every time the user

- initiates a transition to another page in the launcher.

- </summary>

-</histogram>

<owner>tapted@chromium.org</owner>

@@ -499,15 +483,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Apps.AppListSearchResultOpenDisplayType"

- enum="AppListSearchResultDisplayType">

- <owner>calamity@chromium.org</owner>

- <summary>

- The display type of the app list search result that was opened by the user.

- This is gathered per click of a search result.

- </summary>

-</histogram>

<owner>tapted@chromium.org</owner>

@@ -1980,16 +1955,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

-<histogram name="Autofill.ScanCreditCard.Completed" units="BooleanCompleted">

- <owner>rouslan@chromium.org</owner>

- <summary>Whether a credit card scan was completed or cancelled.</summary>

-</histogram>

-<histogram name="Autofill.ScanCreditCard.Duration" units="ms">

- <owner>rouslan@chromium.org</owner>

- <summary>How long a credit card took to scan.</summary>

-</histogram>

<histogram name="Autofill.ScanCreditCardPrompt"

enum="AutofillScanCreditCardPrompt">

<owner>estade@chromium.org</owner>

@@ -2055,6 +2020,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

+<histogram name="Autofill.UnmaskPrompt.Events" enum="AutofillUnmaskPromptEvent">

+ <owner>waltercacau@chromium.org</owner>

+ <summary>Events tracking the usage of the unmasking prompt.</summary>

+</histogram>

<owner>isherman@chromium.org</owner>

@@ -3035,14 +3005,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<summary>Event counts in ServiceProcessControl.</summary>

</histogram>

-<histogram name="CloudPrint.ServiceProcessSocketLength">

- <owner>vitalybuka@chromium.org</owner>

- <summary>

- Temporarily histogram with size of IPC sockets in default location.

- TODO(vitalybuka) Remove after investigation http://crbug.com/466644

- </summary>

-</histogram>

<owner>vitalybuka@chromium.org</owner>

@@ -3371,7 +3333,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <owner>tnagel@chromium.org</owner>

+ <owner>Please list the metric's owners. Add more owner tags as needed.</owner>

Records the detection of a corrupted meta table. See http://crbug.com/111376

@@ -3560,25 +3522,15 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <owner>erikwright@chromium.org</owner>

+ <owner>Please list the metric's owners. Add more owner tags as needed.</owner>

<summary>The amount of time (ms) to migrate a v4 database to v5.</summary>

</histogram>

- <owner>erikwright@chromium.org</owner>

+ <owner>Please list the metric's owners. Add more owner tags as needed.</owner>

<summary>The amount of time (ms) to migrate a v5 database to v6.</summary>

</histogram>

-<histogram name="Cookie.TimeDatabaseMigrationToV7" units="ms">

- <owner>erikwright@chromium.org</owner>

- <summary>The amount of time (ms) to migrate a v6 database to v7.</summary>

-</histogram>

-<histogram name="Cookie.TimeDatabaseMigrationToV8" units="ms">

- <owner>erikwright@chromium.org</owner>

- <summary>The amount of time (ms) to migrate a v7 database to v8.</summary>

-</histogram>

Deprecated as of 11/2014.

@@ -3610,15 +3562,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Cookie.TimeKeyLoadTotalWait" units="ms">

- <owner>erikchen@chromium.org</owner>

- <summary>

- This histogram records the the total amount of time spent fetching the

- cookies associated with an eTLD+1 from disk, including time spent waiting in

- task queues.

- </summary>

-</histogram>

<owner>erikwright@chromium.org</owner>

@@ -3628,7 +3571,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <owner>erikchen@chromium.org</owner>

+ <owner>Please list the metric's owners. Add more owner tags as needed.</owner>

This histogram records the wall-clock delay between the Load task being

posted to the DB-thread and its execution.

@@ -3660,17 +3603,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="CrashReport.PermanentUploadFailure" enum="BooleanHit">

- <owner>erikwright@chromium.org</owner>

- <summary>

- Counts crash reports that the Kasko crash reporter fails to upload and hands

- off to Chrome. Kasko stores the failed reports in a location specified by

- Chrome. Chrome records this metric when it detects new minidump files in

- that location. Currently the reports are discarded, but they could

- eventually be uploaded via the Chrome network stack.

- </summary>

-</histogram>

Deprecated as of 12/2013. Default pinned apps trial is finished.

@@ -5666,9 +5598,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <obsolete>

- Deprecated 2012.

- </obsolete>

<owner>michaeln@chromium.org</owner>

Duration to execute localStorage.clear() or sessionStorage.clear().

@@ -5676,9 +5605,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <obsolete>

- Deprecated 2012.

- </obsolete>

<owner>michaeln@chromium.org</owner>

Duration to execute localStorage.getItem() or sessionStorage.getItem().

@@ -5686,9 +5612,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <obsolete>

- Deprecated 2012.

- </obsolete>

<owner>michaeln@chromium.org</owner>

Duration to execute localStorage.key() or sessionStorage.key().

@@ -5696,9 +5619,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <obsolete>

- Deprecated 2012.

- </obsolete>

<owner>michaeln@chromium.org</owner>

Duration to execute localStorage.length() or sessionStorage.length().

@@ -5706,9 +5626,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <obsolete>

- Deprecated 2012.

- </obsolete>

<owner>michaeln@chromium.org</owner>

Duration to execute localStorage.removeItem() or

@@ -5717,9 +5634,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <obsolete>

- Deprecated 2012.

- </obsolete>

<owner>michaeln@chromium.org</owner>

Duration to execute localStorage.setItem() or sessionStorage.setItem().

@@ -6516,80 +6430,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="EasyUnlock.AuthProximity.RemoteDeviceModelHash"

- enum="EasyUnlockDeviceModelHash">

- <owner>tengs@chromium.org</owner>

- <owner>xiaowenx@chromium.org</owner>

- <summary>

- The hash of the phone model used to successfully sign in or unlock using

- Smart Lock.

- </summary>

- <details>

- This hash is calculated by taking the first 4 bytes of the MD5 hash of the

- device model.

- </details>

-</histogram>

-<histogram name="EasyUnlock.AuthProximity.RollingRssi" units="dBm">

- <owner>tengs@chromium.org</owner>

- <owner>xiaowenx@chromium.org</owner>

- <summary>

- Measures the exponentially weighted rolling average of the received signal

- strength indicator (RSSI) of the phone when the user successfully unlocks or

- signs in using Smart Lock.

- </summary>

- <details>

- The exponentially weighted averaging formula is:

- rollingRssi = (1 - weight) * rollingRssi + weight * currentRssi;

- RSSI readings are inherently noisy, so this averaging gives a smoothed RSSI

- value to work with as a heuristic for proximity.

- If no RSSI was read, then a sentinel value of 127 will be recorded.

- </details>

-</histogram>

-<histogram name="EasyUnlock.AuthProximity.TimeSinceLastZeroRssi"

- units="milliseconds">

- <owner>tengs@chromium.org</owner>

- <owner>xiaowenx@chromium.org</owner>

- <summary>

- Measures the time delta in milliseconds since the last zero RSSI value was

- read to when the user successfully unlocks or signs in using Smart Lock.

- </summary>

- <details>

- A zero RSSI value is special because both Bluetooth devices in a connection

- attempt to maintain by adjusting their transmit power levels. This time

- delta can be used as a possible heuristic to determine that the phone is

- close to the local device.

- If no RSSI was read, then an overflow value will be recorded.

- </details>

-</histogram>

-<histogram name="EasyUnlock.AuthProximity.TransmitPowerDelta" units="dBm">

- <owner>tengs@chromium.org</owner>

- <owner>xiaowenx@chromium.org</owner>

- <summary>

- Measures the difference between the current transmit power and the maximum

- transmit power of the local device when the user successfully unlocks or

- signs in using Smart Lock.

- </summary>

- <details>

- Devices connected using classic Bluetooth adjust their transmit power

- dynamically to optimize power and signal strength. The difference between

- the current transmit power and maximum transmit power can be used as a

- heurstic to determine if the phone is close to the local device.

- According to the Bluetooth specs, there are three classes of devices, with a

- maximum transmit power of 20, 4, and 0 dBm respectively.

- If no transmit power was read, then a sentinel value of 127 will be

- recorded.

- </details>

-</histogram>

<owner>joshwoodward@google.com</owner>

<owner>tbarzic@chromium.org</owner>

@@ -6600,9 +6440,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

enum="EasyUnlockNotificationEvent">

<owner>joshwoodward@google.com</owner>

<owner>tbarzic@chromium.org</owner>

- <obsolete>

- Deprecated 02/2015. Replaced by EasyUnlock.Setup.PromoNotificationEvent.

- </obsolete>

Tracks events related to notifications used by EasyUnlock feature. For

example a specific EasyUnlock notification being shown or clicked.

@@ -6624,98 +6461,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="EasyUnlock.Setup.Devices.Count.Eligible">

- <owner>isherman@chromium.org</owner>

- <owner>xiaowenx@chromium.org</owner>

- <summary>

- The number of eligible devices that the CryptAuth server returns during the

- Smart Lock setup flow.

- </summary>

- <details>

- Note that a single user might report multiple values, for example if she

- tries to complete the setup flow with a device in airplane mode, and then

- tries again taking the device out of airplane mode.

- </details>

-</histogram>

-<histogram name="EasyUnlock.Setup.Devices.Count.Ineligible">

- <owner>isherman@chromium.org</owner>

- <owner>xiaowenx@chromium.org</owner>

- <summary>

- The number of ineligible devices that the CryptAuth server returns during

- the Smart Lock setup flow.

- </summary>

- <details>

- Note that a single user might report multiple values, for example if she

- tries to complete the setup flow with a device in airplane mode, and then

- tries again taking the device out of airplane mode.

- </details>

-</histogram>

-<histogram name="EasyUnlock.Setup.Devices.HasSecureScreenLock"

- enum="EasyUnlockHasSecureScreenLock">

- <owner>isherman@chromium.org</owner>

- <owner>xiaowenx@chromium.org</owner>

- <summary>

- Whether the user's phone has a secure screen lock installed. Recorded during

- Smart Lock setup, when the user's phone first connects to the Chromebook.

- </summary>

-</histogram>

-<histogram name="EasyUnlock.Setup.Devices.HasTrustAgentEnabled"

- enum="EasyUnlockHasTrustAgentEnabled">

- <owner>isherman@chromium.org</owner>

- <owner>xiaowenx@chromium.org</owner>

- <summary>

- Whether the user's phone has a trust agent -- e.g. Smart Lock for Android --

- enabled. Recorded during Smart Lock (for Chrome) setup, when the user's

- phone first connects to the Chromebook.

- </summary>

- <details>

- Note that this histogram tracks whether the setting under Settings ~>

- Security ~> Trust agents ~> Smart Lock (Google) (or any other trust

- agent) is enabled. The Smart Lock trust agent is enabled by default for

- users who have ascure lock screen. This metric does _not_ measure whether

- users have any Smart Lock trustlets enabled.

- </details>

-</histogram>

-<histogram name="EasyUnlock.Setup.Devices.IneligibilityReason"

- enum="EasyUnlockDeviceIneligibilityReason">

- <owner>isherman@chromium.org</owner>

- <owner>xiaowenx@chromium.org</owner>

- <summary>

- Records the most actionable reason why none of a user's devices were

- eligible as unlock keys for Smart Lock. This is recorded during the Smart

- Lock setup flow, only if the CryptAuth server returns no eligible devices

- for the user.

- </summary>

- <details>

- To be precise, this metric tracks the _least_ actionable _reason_ why the

- _most_ actionable _device_ is not eligible as an unlock key. For example,

- suppose that the user has 10 ineligible devices returned. This metric tries

- to identify the most likely candidate device for use as a Smart Lock key,

- and then records the most confounding reason why that device is still not

- eligible to be used as an unlock key.

- </details>

-</histogram>

-<histogram name="EasyUnlock.Setup.PromoNotificationEvent"

- enum="EasyUnlockPromoNotificationEvent">

- <owner>isherman@chromium.org</owner>

- <owner>xiaowenx@chromium.org</owner>

- <summary>

- Measures user interactions with the Smart Lock promo notification.

- </summary>

- <details>

- Due to technical limitations of the implementation, it is hard to track

- precisely which users opened the setup app as a result of interacting with

- the promo notification. This metric measures setup app interactions from all

- users who click on the promo notification, and subsequently launch the setup

- app.

- </details>

-</histogram>

<owner>joshwoodward@google.com</owner>

<owner>tbarzic@chromium.org</owner>

@@ -6751,23 +6496,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="EasyUnlock.TrialRun.Events" enum="EasyUnlockTrialRunEvents">

- <owner>isherman@chromium.org</owner>

- <owner>xiaowenx@chromium.org</owner>

- <summary>

- Records when the Easy Unlock trial run is launched, and when the user

- attempts to click on the lock icon during the trial run.

- </summary>

- <details>

- If a user clicks on the lock icon more than once, then the "clicked

- lock icon" event counter will be incremented more than once as well.

- Hence, the "user count" data shows how many users ever clicked on

- the lock icon during the trial run. From the raw (non-"user

- count") data, we can also see whether users click on the icon multiple

- times.

- </details>

-</histogram>

Deprecated 02/2015; replaced by EasyUnlock.AuthEvent.Unlock.

@@ -8470,32 +8198,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Extensions.BadMessageFunctionName" enum="ExtensionFunctions">

- <owner>kalman@chromium.org</owner>

- <summary>

- The number of times each Extension function call sends a bad message,

- killing the renderer. This may indicate a bug in that API's implementation

- on the renderer. Note a similar, aggregate metric is BadMessageTerminate_EFD

- which counts the number of bad messages that are sent overall.

- </summary>

-</histogram>

-<histogram name="Extensions.BadSyncDataReason" enum="BadSyncDataReason">

- <owner>yoz@chromium.org</owner>

- <summary>

- The reason a valid ExtensionSyncData could not be parsed from a SyncData

- received from sync.

- </summary>

-</histogram>

-<histogram name="Extensions.CheckForExternalUpdatesTime">

- <owner>rkaplow@chromium.org</owner>

- <summary>

- The amount of time that elapsed during

- ExtensionService::CheckForExternalUpdates.

- </summary>

-</histogram>

<owner>asargent@chromium.org</owner>

@@ -8771,42 +8473,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Extensions.ExtensionHostMonitoring.MaxActiveLoading">

- <owner>kalman@chromium.org</owner>

- <summary>

- The maximum number of ExtensionHosts (primarily background/event pages) that

- were actively loading at any one time, within the first minute of Chrome

- startup. Emitted exactly one minute after startup.

- </summary>

-</histogram>

-<histogram name="Extensions.ExtensionHostMonitoring.MaxInQueue">

- <owner>kalman@chromium.org</owner>

- <summary>

- The maximum number of ExtensionHosts (primarily background/event pages) in

- the queue awaiting being loaded (via an ExtensionHostQueue), within the

- first minute of Chrome startup. Emitted exactly one minute after startup.

- </summary>

-</histogram>

-<histogram name="Extensions.ExtensionHostMonitoring.NumLoaded">

- <owner>kalman@chromium.org</owner>

- <summary>

- The total number of ExtensionHosts that completed loading in the first

- minute of Chrome startup. Emitted exactly one minute after startup.

- </summary>

-</histogram>

-<histogram name="Extensions.ExtensionHostMonitoring.NumQueued">

- <owner>kalman@chromium.org</owner>

- <summary>

- The total number of ExtensionHosts (primarily background/event pages) that

- were added to a queue to start loading, within the first minute of Chrome

- startup. These may or may not end up starting, let alone finishing,

- depending on the queue behavior. Emitted exactly one minute after startup.

- </summary>

-</histogram>

<owner>kalman@chromium.org</owner>

<summary>An extension has been installed.</summary>

@@ -8820,14 +8486,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Extensions.ExtensionManagement_RefreshTime"

- units="milliseconds">

- <owner>rkaplow@chromium.org</owner>

- <summary>

- The amount of time that elapsed during ExtensionManagement::Refresh.

- </summary>

-</histogram>

<owner>Please list the metric's owners. Add more owner tags as needed.</owner>

@@ -8884,15 +8542,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Extensions.FeatureProviderStaticInitTime" units="milliseconds">

- <owner>rkaplow@chromium.org</owner>

- <summary>

- The amount of time that elapsed during

- extensions::FeatureProvider::Static. Only measured while in the browser

- process.

- </summary>

-</histogram>

<owner>kalman@chromium.org</owner>

@@ -9020,14 +8669,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Extensions.InjectEnd_BlockingScriptCount">

- <owner>kalman@chromium.org</owner>

- <owner>rdevlin.cronin@chromium.org</owner>

- <summary>

- Number of blocking scripts injected at document end by extensions.

- </summary>

-</histogram>

<owner>kalman@chromium.org</owner>

<owner>rdevlin.cronin@chromium.org</owner>

@@ -9042,14 +8683,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Extensions.InjectIdle_BlockingScriptCount">

- <owner>kalman@chromium.org</owner>

- <owner>rdevlin.cronin@chromium.org</owner>

- <summary>

- Number of blocking scripts injected at document idle by extensions.

- </summary>

-</histogram>

<owner>kalman@chromium.org</owner>

<owner>rdevlin.cronin@chromium.org</owner>

@@ -9070,14 +8703,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<summary>Time taken to inject all scripts by extensions.</summary>

</histogram>

-<histogram name="Extensions.InjectStart_BlockingScriptCount">

- <owner>kalman@chromium.org</owner>

- <owner>rdevlin.cronin@chromium.org</owner>

- <summary>

- Number of blocking scripts injected at document start by extensions.

- </summary>

-</histogram>

<owner>kalman@chromium.org</owner>

<owner>rdevlin.cronin@chromium.org</owner>

@@ -9167,15 +8792,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Extensions.LoadAllTime2" units="milliseconds">

- <owner>kalman@chromium.org</owner>

- <summary>

- Time taken to load all non-component extensions at browser startup and

- record metrics. This happens as part of the total initialization time of

- ExtensionService, measured in Extensions.ExtensionServiceInitTime.

- </summary>

-</histogram>

<owner>kalman@chromium.org</owner>

<summary>The number of apps loaded by each user at startup time.</summary>

@@ -10851,25 +10467,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<summary>The HRESULT for a failed on-demand update check.</summary>

</histogram>

-<histogram name="GoogleUpdate.InfoBar.ActionTaken"

- enum="GoogleUpdateInfoBarActions">

- <owner>yfriedman@chromium.org</owner>

- <owner>dfalcantara@chromium.org</owner>

- <summary>

- (Android-only) Records what action the user took (if any) on the InfoBar

- indicating that a new version of Chrome is available.

- </summary>

-</histogram>

-<histogram name="GoogleUpdate.InfoBar.TimeShown" units="milliseconds">

- <owner>yfriedman@chromium.org</owner>

- <owner>dfalcantara@chromium.org</owner>

- <summary>

- (Android-only) The amount of time which the InfoBar indicating a new version

- is available is visible.

- </summary>

-</histogram>

<owner>grt@chromium.org</owner>

<summary>The error code for a failed on-demand update check.</summary>

@@ -12504,13 +12101,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<summary>Application languages used for UI.</summary>

</histogram>

-<histogram name="Launch.HomeScreen" enum="LaunchFromHomeScreen">

- <owner>dfalcantara@chromium.org</owner>

- <summary>

- Records how Chrome handled a launch from an Android Home screen shortcut.

- </summary>

-</histogram>

Deprecated 2013-10. No thread-unsafety was found.

@@ -12757,15 +12347,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Linux.SandboxStatus" enum="LinuxSandboxStatus">

- <owner>rickyz@chromium.org</owner>

- <summary>

- The Linux sandbox status. This describes what sandboxing features are

- enabled (such as the suid/namespace sandboxes, various namespaces, seccomp

- bpf, ...). Emitted once at startup.

- </summary>

-</histogram>

<owner>pkotwicz@chromium.org</owner>

@@ -12838,14 +12419,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="LocalStorage.CommitDelay">

- <owner>michaeln@chromium.org</owner>

- <summary>

- Delay between a page making changes and those changes being written to the

- DB.

- </summary>

-</histogram>

<owner>michaeln@chromium.org</owner>

@@ -14142,14 +13715,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Memory.DiscardableAllocationSize" units="KB">

- <owner>reveman@chromium.org</owner>

- <summary>

- The discardable memory allocation size in KB. Recorded each time a new

- discardable memory instance is created.

- </summary>

-</histogram>

<owner>hajimehoshi@chromium.org</owner>

<owner>kenjibaheux@google.com</owner>

@@ -14716,14 +14281,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="MobileFre.SignInChoice" enum="MobileFreSignInChoice">

- <owner>aruslan@chromium.org</owner>

- <summary>

- Android: How the user left the sign-in part of the "first run

- experience" activity (M-38+).

- </summary>

-</histogram>

<histogram name="MobileFullscreenVideo.DurationAfterPotraitRotation"

units="milliseconds">

<owner>qinmin@chromium.org</owner>

@@ -15615,15 +15172,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Navigation.IsMobileOptimized" enum="BooleanIsMobileOptimized">

- <owner>cjhopman@chromium.org</owner>

- <owner>nyquist@chromium.org</owner>

- <summary>

- Signifies whether a succesfully finished page load for the main frame

- content width fits within the device width and/or has a fixed page scale.

- </summary>

-</histogram>

<owner>cbentzel@chromium.org</owner>

<owner>davidben@chromium.org</owner>

@@ -16811,7 +16359,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <owner>davidben@chromium.org</owner>

+ <owner>Please list the metric's owners. Add more owner tags as needed.</owner>

Each bucket is the number of successful connections of a particular type

that the user has had during the session.

@@ -17782,16 +17330,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Net.GzipEncodingFixupResult" enum="GzipEncodingFixupResult">

- <owner>asanka@chromium.org</owner>

- <summary>

- Resources are sometimes transferred with an incorrect encoding type of gzip.

- net::Filter::FixupEncodingTypes() attempts to correct for these situations

- by applying a set of heuristics. This histogram counts the frequency of

- usage of these heuristics in the wild.

- </summary>

-</histogram>

The count was inaccurate (it counted transactions rather than connections).

@@ -17816,7 +17354,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <owner>davidben@chromium.org</owner>

+ <owner>Please list the metric's owners. Add more owner tags as needed.</owner>

Each bucket is a boolean (0 or 1) indicating whether the user has had a

successful connection of that type during the session.

@@ -19085,7 +18623,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Net.QuicSession.AsyncRead" enum="Boolean">

+<histogram name="Net.QuicSession.AsyncRead">

<owner>rch@chromium.org</owner>

True if the result of reading a packet from the network was ERR_IO_PENDING.

@@ -19109,7 +18647,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Net.QuicSession.ClosedDuringInitializeSession" enum="Boolean">

+<histogram name="Net.QuicSession.ClosedDuringInitializeSession">

<owner>rch@chromium.org</owner>

True if the QUIC session is closed during the call to InitializeSession,

@@ -19303,16 +18841,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Net.QuicSession.HostResolution.HandshakeConfirmedTime"

- units="Milliseconds">

- <owner>rtenneti@chromium.org</owner>

- <summary>

- The elapsed time between the end of resolving the DNS name of the server for

- a QUIC connection, and receiving crypto handshake confirmation from the

- server. Logged after crypto handshake is confirmed.

- </summary>

-</histogram>

<owner>rch@chromium.org</owner>

@@ -19599,7 +19127,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

enum="QuicSessionLocations">

<owner>rch@chromium.org</owner>

- The location in quic_client_session.cc where a session is unexpectedly

+ The location in quic_client_session.cc where a session is unexpectedly

not going away.

</summary>

</histogram>

@@ -20190,10 +19718,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<owner>agl@chromium.org</owner>

<owner>rsleevi@chromium.org</owner>

- <summary>

- The SSL/TLS cipher suite that was negotiated. Recorded for each SSL/TLS

- connection in the socket pool where Connect() succeeds.

- </summary>

+ <summary>The SSL/TLS cipher suite that was negotiated.</summary>

</histogram>

@@ -20382,14 +19907,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<summary>Time saved by a speculative certificate vertification.</summary>

</histogram>

-<histogram name="Net.SSLVersion" enum="SSLOrQUICVersion">

- <owner>davidben@chromium.org</owner>

- <summary>

- The SSL/TLS version that was negotiated. Recorded for each SSL/TLS

- connection in the socket pool where Connect() succeeds.

- </summary>

-</histogram>

<owner>Please list the metric's owners. Add more owner tags as needed.</owner>

<summary>Number of idle sockets when the Connect() succeeded.</summary>

@@ -23570,15 +23087,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Omnibox.CharTypedToRepaintLatency">

- <owner>asvitkine@chromium.org</owner>

- <summary>

- Records the time taken between a keystroke being typed in the omnibox and

- the text being painted. If there are multiple keystrokes before a paint,

- logs the time since the earliest one.

- </summary>

-</histogram>

<owner>mpearson@chromium.org</owner>

@@ -24348,9 +23856,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<histogram name="PasswordManager.AllowToCollectURLBubble.UIDismissalReason"

enum="PasswordManagerAllowToCollectURLBubble.UIDismissalReason">

- <obsolete>

- The bubble isn't shown anymore.

- </obsolete>

<owner>melandory@chromium.org</owner>

<owner>vasilii@chromium.org</owner>

<summary>Why was "Allow to collect URL?" bubble closed?</summary>

@@ -27239,15 +26744,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Plugin.PowerSaver.PosterParamPresence"

- enum="PluginPowerSaverPosterParamPresence">

- <owner>tommycli@chromium.org</owner>

- <summary>

- Record how many plugin object tags use poster param. This is recorded once

- per plugin instance, and is currently restricted to Flash plugin instances.

- </summary>

-</histogram>

<histogram name="Plugin.PowerSaver.Unthrottle"

enum="PluginPowerSaverUnthrottleMethod">

<owner>tommycli@chromium.org</owner>

@@ -27912,11 +27408,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="PrefService.CreateProfilePrefsTime" units="milliseconds">

- <owner>rkaplow@chromium.org</owner>

- <summary>The amount of time that elapsed during CreateProfilePrefs.</summary>

-</histogram>

<owner>davidben@chromium.org</owner>

<owner>tburkard@chromium.org</owner>

@@ -27928,9 +27419,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <obsolete>

- Deprecated March 13 2015.

- </obsolete>

<owner>tburkard@chromium.org</owner>

Enumeration of what types of cookies were sent for a prerender.

@@ -27938,9 +27426,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <obsolete>

- Deprecated March 13 2015.

- </obsolete>

<owner>tburkard@chromium.org</owner>

<summary>Enumeration of what cookie actions a prerender caused.</summary>

</histogram>

@@ -28841,22 +28326,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="PrintPreview.PageCount.PrintWithExtension">

- <owner>vitalybuka@chromium.org</owner>

- <summary>

- The final page count (after page selection) of documents printed to an

- extension printer (using printerProvider API).

- </summary>

-</histogram>

-<histogram name="PrintPreview.PageCount.PrintWithPrivet">

- <owner>vitalybuka@chromium.org</owner>

- <summary>

- The final page count (after page selection) of documents printed to a privet

- printer.

- </summary>

-</histogram>

<owner>vitalybuka@chromium.org</owner>

@@ -28998,19 +28467,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<summary>Size of the cookies database.</summary>

</histogram>

-<histogram name="Profile.CreateAndInitializeProfile" units="milliseconds">

- <owner>rkaplow@chromium.org</owner>

- <summary>Length of time to setup profile.</summary>

-</histogram>

-<histogram name="Profile.CreateProfileHelperTime" units="milliseconds">

- <owner>rkaplow@chromium.org</owner>

- <summary>

- The amount of time that elapsed during ProfileManager::CreateProfileHelper.

- This is called when a profile is created synchronously (usually at startup).

- </summary>

-</histogram>

<owner>pam@chromium.org</owner>

<owner>rlp@chromium.org</owner>

@@ -29100,9 +28556,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <obsolete>

- Deprecated 02/2015. Profile.CreateAndInitializeProfile is more useful.

- </obsolete>

<owner>rkaplow@chromium.org</owner>

<summary>Length of time to retrieve profile.</summary>

</histogram>

@@ -29277,13 +28730,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Profile.OnPrefsLoadedTime" units="milliseconds">

- <owner>rkaplow@chromium.org</owner>

- <summary>

- The amount of time that elapsed during ProfileImpl::OnPrefsLoaded.

- </summary>

-</histogram>

Deprecated because it did not present the information clearly.

@@ -29314,7 +28760,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <owner>tnagel@chromium.org</owner>

+ <owner>Please list the metric's owners. Add more owner tags as needed.</owner>

The error with the current user profile that caused an error dialog to be

shown. This dialog is shown usually when there is some sort of corruption in

@@ -29494,26 +28940,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="PushMessaging.DeliveryStatus" enum="PushDeliveryStatus">

- <owner>johnme@google.com</owner>

- <owner>mvanouwerkerk@google.com</owner>

- <summary>

- When a Service Worker receives a push message, this records whether it was

- successful, or otherwise the type of error encountered.

- </summary>

-</histogram>

-<histogram name="PushMessaging.GetRegistrationStatus"

- enum="PushGetRegistrationStatus">

- <owner>johnme@google.com</owner>

- <owner>mvanouwerkerk@google.com</owner>

- <summary>

- When a webpage asks for details about its current push messaging

- registration, this records whether the request is successful, or otherwise

- the type of error encountered.

- </summary>

-</histogram>

<histogram name="PushMessaging.RegistrationStatus"

enum="PushRegistrationStatus">

<owner>johnme@google.com</owner>

@@ -29524,16 +28950,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="PushMessaging.UnregistrationStatus"

- enum="PushUnregistrationStatus">

- <owner>johnme@google.com</owner>

- <owner>mvanouwerkerk@google.com</owner>

- <summary>

- When a webpage unregisters from push messaging, this records whether the

- request is successful, or otherwise the type of error encountered.

- </summary>

-</histogram>

<owner>johnme@google.com</owner>

<owner>mvanouwerkerk@google.com</owner>

@@ -30571,7 +29987,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <owner>estade@chromium.org</owner>

+ <owner>Please list the metric's owners. Add more owner tags as needed.</owner>

Measures the duration for which an requestAutocomplete() dialog was shown.

</summary>

@@ -33423,15 +32839,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Sdch3.PersistenceFailureReason"

- enum="SdchPersistenceFailureReason">

- <owner>rdsmith@chromium.org</owner>

- <summary>

- Tracks failures that occur when reading in or writing out persisted

- dictionary information.

- </summary>

-</histogram>

Deprecated 2014-11. Sdch3.ProblemCodes_5 used instead.

@@ -33659,30 +33066,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="ServiceWorker.StartWorker.Status"

- units="ServiceWorkerStatusCode">

- <owner>falken@chromium.org</owner>

- <summary>The result of trying to start a Service Worker.</summary>

-</histogram>

-<histogram name="ServiceWorker.StartWorker.Time" units="milliseconds">

- <owner>falken@chromium.org</owner>

- <summary>

- The time taken to start a Service Worker end-to-end, from process allocation

- to ACK of started from the renderer. This possibly includes script download

- time, but the metric is not recorded if DevTools was ever attached to the

- Service Worker during startup.

- </summary>

-</histogram>

-<histogram name="ServiceWorker.StartWorker.TimeoutPhase"

- units="EmbeddedWorkerStartingPhase">

- <owner>falken@chromium.org</owner>

- <summary>

- The phase the EmbeddedWorker was in when ServiceWorker startup timed out.

- </summary>

-</histogram>

<owner>dmurph@chromium.org</owner>

@@ -33699,14 +33082,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Session.TotalDuration" units="milliseconds">

- <owner>mariakhomenko@chromium.org</owner>

- <owner>fqian@chromium.org</owner>

- <summary>

- The length of a session (launch/foregrounding to backgrounding) on mobile.

- </summary>

-</histogram>

<owner>yiyaoliu@chromium.org</owner>

<summary>How did the user interact with the SessionCrashed Bubble?</summary>

@@ -34017,13 +33392,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<summary>The number of pinned tabs opened when a profile is loaded.</summary>

</histogram>

-<histogram name="Settings.RegisterProfilePrefsTime" units="milliseconds">

- <owner>rkaplow@chromium.org</owner>

- <summary>

- The amount of time that elapsed during RegisterProfilePrefs.

- </summary>

-</histogram>

<owner>mpearson@chromium.org</owner>

@@ -37903,33 +37271,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Startup.PreMainMessageLoopRunImplStep1Time"

- units="milliseconds">

- <owner>rkaplow@chromium.org</owner>

- <summary>

- The amount of time that elapsed during the first untracked section of

- ChromeBrowserMainParts::PreMainMessageLoopRunImpl.

- </summary>

-</histogram>

-<histogram name="Startup.PreMainMessageLoopRunImplStep2Time"

- units="milliseconds">

- <owner>rkaplow@chromium.org</owner>

- <summary>

- The amount of time that elapsed during the second untracked section of

- ChromeBrowserMainParts::PreMainMessageLoopRunImpl. Not written for Android.

- </summary>

-</histogram>

-<histogram name="Startup.PreMainMessageLoopRunImplStep3Time"

- units="milliseconds">

- <owner>rkaplow@chromium.org</owner>

- <summary>

- The amount of time that elapsed during the third untracked section of

- ChromeBrowserMainParts::PreMainMessageLoopRunImpl. Not written for Android.

- </summary>

-</histogram>

Deprecated as of 2/2015.

@@ -38047,9 +37388,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<histogram name="Startup.StartupBrowserCreator_ProcessCmdLineImplTime"

units="milliseconds">

- <obsolete>

- Deprecated 02/2015. Startup.StartupBrowserCreator_Start is more useful.

- </obsolete>

<owner>rkaplow@chromium.org</owner>

The amount of time that elapsed during

@@ -38057,13 +37395,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="Startup.StartupBrowserCreator_Start" units="milliseconds">

- <owner>rkaplow@chromium.org</owner>

- <summary>

- The amount of time that elapsed during StartupBrowserCreator::Start().

- </summary>

-</histogram>

<histogram name="Startup.WarmStartTimeFromRemoteProcessStart"

units="milliseconds">

<owner>jeremy@chromium.org</owner>

@@ -40390,23 +39721,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="UMA.EnrollmentStatus" enum="EnrollmentStatus">

- <owner>asvitkine@chromium.org</owner>

- <owner>kaznacheev@chromium.org</owner>

- <summary>

- Logs the device enrollment status for Chrome OS device. Logged with every

- UMA upload.

- </summary>

-</histogram>

-<histogram name="UMA.EntropySourceType" enum="UmaEntropySourceType">

- <owner>asvitkine@chromium.org</owner>

- <summary>

- Logs the entropy source type that was used for field trial randomization.

- Logged once at each start up.

- </summary>

-</histogram>

Deprecated 2012. No longer tracked.

@@ -41436,15 +40750,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<summary>Time spent generating deferred code stubs.</summary>

</histogram>

-<histogram name="V8.DetachedContextAgeInGC">

- <owner>ulan@chromium.org</owner>

- <summary>

- Number of garbage collections that a detached global context survives,

- recorded after each major garbage collection. Values greater than 7 indicate

- a memory leak.

- </summary>

-</histogram>

This histogram is no longer present in V8

@@ -43831,52 +43136,13 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</summary>

</histogram>

-<histogram name="WebsiteSettings.Menu.PermissionChanged" enum="ContentType">

- <owner>miguelg@chromium.org</owner>

- <owner>finnur@chromium.org</owner>

- <summary>

- Count of how often a specific content type (permission) is changed using the

- content settings menu.

- </summary>

-</histogram>

-<histogram name="WebsiteSettings.Menu.PermissionChanged.Allowed"

- enum="ContentType">

- <owner>miguelg@chromium.org</owner>

- <owner>finnur@chromium.org</owner>

- <summary>

- Count of how often a specific content type (permission) is set to 'Allowed'

- using the content settings menu.

- </summary>

-</histogram>

-<histogram name="WebsiteSettings.Menu.PermissionChanged.Blocked"

- enum="ContentType">

- <owner>miguelg@chromium.org</owner>

- <owner>finnur@chromium.org</owner>

- <summary>

- Count of how often a specific content type (permission) is set to 'Blocked'

- using the content settings menu.

- </summary>

-</histogram>

-<histogram name="WebsiteSettings.Menu.PermissionChanged.Reset"

- enum="ContentType">

- <owner>miguelg@chromium.org</owner>

- <owner>finnur@chromium.org</owner>

- <summary>

- Count of how often a specific content type (permission) is reset to the

- default value using the content settings menu.

- </summary>

-</histogram>

<histogram name="WebsiteSettings.OriginInfo.PermissionChanged"

enum="ContentType">

<owner>sashab@chromium.org</owner>

<owner>felt@chromium.org</owner>

Count of how often a specific content type (permission) is changed using the

- Origin Info dialog.

+ Origin Info dialog on Android.

</summary>

</histogram>

@@ -43886,7 +43152,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<owner>felt@chromium.org</owner>

Count of how often a specific content type (permission) is set to 'Allowed'

- using the Origin Info dialog.

+ using the Origin Info dialog on Android.

</summary>

</histogram>

@@ -43896,7 +43162,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<owner>felt@chromium.org</owner>

Count of how often a specific content type (permission) is set to 'Blocked'

- using the Origin Info dialog.

+ using the Origin Info dialog on Android.

</summary>

</histogram>

@@ -44001,16 +43267,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<summary>Number of times that each menu item is clicked.</summary>

</histogram>

-<histogram name="WrenchMenu.OpeningAnimationFrameTimes" units="milliseconds">

- <owner>kkimlabs@chromium.org</owner>

- <summary>

- Frame times of the Android wrench menu opening animation. For example, if

- the menu opening animation runs exactly at 60fps for a second, then each

- frame time is 16ms, and a total of 60 values of 16ms are recorded. If the

- animation is janky, we will see values greater than 16ms in the histogram.

- </summary>

-</histogram>

<owner>rpop@chromium.org</owner>

@@ -44028,7 +43284,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</histogram>

- <owner>kkimlabs@chromium.org</owner>

+ <owner>kkimlabs@google.com</owner>

Time difference between touch down and touch up on Android wrench button.

</summary>

@@ -44253,7 +43509,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

- <int value="2" label="Apps Page context menu"/>

</enum>

@@ -44321,11 +43576,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="AppListDoodleAction" type="int">

- <int value="0" label="DOODLE_SHOWN"/>

- <int value="1" label="DOODLE_CLICKED"/>

-</enum>

@@ -44335,13 +43585,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="AppListPage" type="int">

- <int value="0" label="APPS"/>

- <int value="1" label="SEARCH_RESULTS"/>

- <int value="2" label="START"/>

- <int value="3" label="CUSTOM_LAUNCHER_PAGE"/>

-</enum>

@@ -44351,13 +43594,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="AppListSearchResultDisplayType" type="int">

- <int value="0" label="NONE"/>

- <int value="1" label="LIST"/>

- <int value="2" label="TILE"/>

- <int value="3" label="RECOMMENDATION"/>

-</enum>

@@ -44801,6 +44037,20 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

+<enum name="AutofillUnmaskPromptEvent" type="int">

+ <int value="0" label="Shown"/>

+ <int value="1" label="Closed with no attempts"/>

+ <int value="2" label="Closed with only failed attempts"/>

+ <int value="3" label="Closed with successful attempt"/>

+ <int value="4" label="Card saved locally"/>

+ <int value="5" label="Did opt in to local save"/>

+ <int value="6"

+ label="Did not opt in of local save (local save stayed disabled)"/>

+ <int value="7" label="Did opt out to local save"/>

+ <int value="8"

+ label="Did not opt out of local save (local save stayed enabled)"/>

+</enum>

@@ -44829,13 +44079,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="BadSyncDataReason" type="int">

- <int value="0" label="Bad extension ID"/>

- <int value="1" label="Bad version"/>

- <int value="2" label="Bad update URL"/>

- <int value="3" label="No ExtensionSpecifics"/>

-</enum>

@@ -45055,11 +44298,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="BooleanIsMobileOptimized" type="int">

- <int value="0" label="Not mobile optimized web page"/>

- <int value="1" label="Mobile optimized web page"/>

-</enum>

@@ -46909,41 +46147,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="EasyUnlockDeviceIneligibilityReason" type="int">

- <int value="0" label="Unrecognized reason">

- The server reported a reason that the client is not aware of. This should

- only be recorded if the client's list of possible reasons is out of date.

- </int>

- <int value="1" label="Unknown">

- The server returned the value "Unknown".

- </int>

- <int value="2" label="Screen too large"/>

- <int value="3" label="Phone lacks Bluetooth"/>

- <int value="4" label="Bad OS version"/>

- <int value="5" label="Bad software version (GMS Core)"/>

- <int value="6" label="Auto unlocking not supported"/>

- <int value="7" label="Invalid credentials"/>

- <int value="8" label="Device offline"/>

- <int value="9" label="No recent updates"/>

-</enum>

-<enum name="EasyUnlockDeviceModelHash" type="int">

- <int value="-1168032746" label="Motorola Nexus 6"/>

- <int value="-617422855" label="LGE Nexus 4"/>

- <int value="1286382027" label="Motorola XT1095"/>

- <int value="1881443083" label="LGE Nexus 5"/>

-</enum>

-<enum name="EasyUnlockHasSecureScreenLock" type="int">

- <int value="0" label="Lacks secure screen lock"/>

- <int value="1" label="Has secure screen lock"/>

-</enum>

-<enum name="EasyUnlockHasTrustAgentEnabled" type="int">

- <int value="0" label="No trust agents enabled"/>

- <int value="1" label="1+ trust agents enabled"/>

-</enum>

@@ -46951,14 +46154,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="EasyUnlockPromoNotificationEvent" type="int">

- <int value="0" label="Promo notification shown"/>

- <int value="1" label="Promo notification clicked"/>

- <int value="2" label="Promo notification dismissed"/>

- <int value="3" label="Setup app launched"/>

- <int value="4" label="Setup completed successfully"/>

-</enum>

@@ -46980,33 +46175,11 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="EasyUnlockTrialRunEvents" type="int">

- <int value="0" label="Trial run launched"/>

- <int value="1" label="User clicked lock icon"/>

-</enum>

</enum>

-<enum name="EmbeddedWorkerStartingPhase" type="int">

- <int value="0" label="NOT_STARTING"/>

- <int value="1" label="ALLOCATING_PROCESS"/>

- <int value="2" label="REGISTERING_TO_DEVTOOLS"/>

- <int value="3" label="SENT_START_WORKER"/>

- <int value="4" label="SCRIPT_DOWNLOADING"/>

- <int value="5" label="SCRIPT_LOADED"/>

- <int value="6" label="SCRIPT_EVALUATED"/>

-</enum>

-<enum name="EnrollmentStatus" type="int">

- <int value="0" label="Non-managed"/>

- <int value="1" label="Managed EDU"/>

- <int value="2" label="Managed non-EDU"/>

- <int value="3" label="Error"/>

-</enum>

Defined as DomainCheckErrors in

@@ -47648,10 +46821,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

<int value="291"

label="Report session statistics such as which app was run."/>

- <int value="293"

- label="Send monitoring heartbeats to the management server."/>

- <int value="294" label="How often the monitoring heartbeats are sent."/>

- <int value="295" label="Captive portal authentication ignores proxy"/>

</enum>

@@ -48006,7 +47175,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

- <int value="76" label="DELETED_DEVELOPERPRIVATE_ENABLE"/>

+ <int value="76" label="DEVELOPERPRIVATE_ENABLE"/>

@@ -48912,24 +48081,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

- <int value="964" label="AUDIOMODEM_TRANSMIT"/>

- <int value="965" label="AUDIOMODEM_STOPTRANSMIT"/>

- <int value="966" label="AUDIOMODEM_RECEIVE"/>

- <int value="967" label="AUDIOMODEM_STOPRECEIVE"/>

- <int value="968" label="WEBRTCLOGGINGPRIVATE_STORE"/>

- <int value="969" label="WEBRTCLOGGINGPRIVATE_UPLOADSTORED"/>

- <int value="970" label="FILEMANAGERPRIVATE_SETENTRYTAG"/>

- <int value="971" label="INPUTMETHODPRIVATE_FETCHALLDICTIONARYWORDS"/>

- <int value="972" label="INPUTMETHODPRIVATE_ADDWORDTODICTIONARY"/>

- <int value="973"

- label="WEBSTOREPRIVATE_SHOWPERMISSIONPROMPTFORDELEGATEDINSTALL"/>

- <int value="974" label="PRINTERPROVIDERINTERNAL_GETPRINTDATA"/>

- <int value="975" label="VIRTUALKEYBOARDPRIVATE_SETMODE"/>

- <int value="976" label="NETWORKINGPRIVATE_STARTACTIVATE"/>

- <int value="977" label="FILEMANAGERPRIVATE_GRANTACCESS"/>

- <int value="978" label="DEVELOPERPRIVATE_GETEXTENSIONSINFO"/>

- <int value="979" label="DEVELOPERPRIVATE_GETEXTENSIONINFO"/>

- <int value="980" label="FILEMANAGERPRIVATE_ENABLEEXTERNALFILESCHEME"/>

</enum>

@@ -50734,13 +49885,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="GoogleUpdateInfoBarActions" type="int">

- <int value="0" label="Clicked close"/>

- <int value="1" label="Clicked to update but failed"/>

- <int value="2" label="Clicked to update appears successful"/>

- <int value="3" label="InfoBar dismissed implicitly (no interaction)"/>

-</enum>

@@ -50750,13 +49894,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="GzipEncodingFixupResult" type="int">

- <int value="0" label="Gzip encoding left as-is"/>

- <int value="1" label="MIME type indicated GZIP content"/>

- <int value="2" label="Explicit download with GZIP filename extension"/>

- <int value="3" label="Unhandled MIME type with a GZIP filename extension"/>

-</enum>

<summary>Possible detected devices combination on leaving dialog</summary>

@@ -52171,11 +51308,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

</enum>

-<enum name="LaunchFromHomeScreen" type="int">

- <int value="0" label="Launched as standalone web app"/>

- <int value="1" label="Launched as a tab"/>

-</enum>

@@ -52335,153 +51467,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.

- <int value="11" label="2.20"/>

- <int value="12" label="2.21"/>

- <int value="13" label="2.22"/>

- <int value="14" label="2.23"/>

- <int value="15" label="2.24"/>

- <int value="16" label="2.25"/>

- <int value="17" label="2.26"/>

- <int value="18" label="2.27"/>

- <int value="19" label="2.28"/>

- <int value="20" label="2.29"/>

-</enum>

-<enum name="LinuxSandboxStatus" type="int">

- <int value="0" label="none"/>

- <int value="1" label="suid"/>

- <int value="2" label="pidns"/>

- <int value="3" label="suid, pidns"/>

- <int value="4" label="netns"/>

- <int value="5" label="suid, netns"/>

- <int value="6" label="pidns, netns"/>

- <int value="7" label="suid, pidns, netns"/>

- <int value="8" label="seccomp-bpf"/>

- <int value="9" label="suid, seccomp-bpf"/>

- <int value="10" label="pidns, seccomp-bpf"/>

- <int value="11" label="suid, pidns, seccomp-bpf"/>

- <int value="12" label="netns, seccomp-bpf"/>

- <int value="13" label="suid, netns, seccomp-bpf"/>

- <int value="14" label="pidns, netns, seccomp-bpf"/>

- <int value="15" label="suid, pidns, netns, seccomp-bpf"/>

- <int value="16" label="yama"/>

- <int value="17" label="suid, yama"/>

- <int value="18" label="pidns, yama"/>

- <int value="19" label="suid, pidns, yama"/>

- <int value="20" label="netns, yama"/>

- <int value="21" label="suid, netns, yama"/>

- <int value="22" label="pidns, netns, yama"/>

- <int value="23" label="suid, pidns, netns, yama"/>

- <int value="24" label="seccomp-bpf, yama"/>

- <int value="25" label="suid, seccomp-bpf, yama"/>

- <int value="26" label="pidns, seccomp-bpf, yama"/>

- <int value="27" label="suid, pidns, seccomp-bpf, yama"/>

- <int value="28" label="netns, seccomp-bpf, yama"/>

- <int value="29" label="suid, netns, seccomp-bpf, yama"/>

- <int value="30" label="pidns, netns, seccomp-bpf, yama"/>

- <int value="31" label="suid, pidns, netns, seccomp-bpf, yama"/>

- <int value="32" label="seccomp-tsync"/>

- <int value="33" label="suid, seccomp-tsync"/>

- <int value="34" label="pidns, seccomp-tsync"/>

- <int value="35" label="suid, pidns, seccomp-tsync"/>

- <int value="36" label="netns, seccomp-tsync"/>

- <int value="37" label="suid, netns, seccomp-tsync"/>

- <int value="38" label="pidns, netns, seccomp-tsync"/>

- <int value="39" label="suid, pidns, netns, seccomp-tsync"/>

- <int value="40" label="seccomp-bpf, seccomp-tsync"/>

- <int value="41" label="suid, seccomp-bpf, seccomp-tsync"/>

- <int value="42" label="pidns, seccomp-bpf, seccomp-tsync"/>

- <int value="43" label="suid, pidns, seccomp-bpf, seccomp-tsync"/>

- <int value="44" label="netns, seccomp-bpf, seccomp-tsync"/>

- <int value="45" label="suid, netns, seccomp-bpf, seccomp-tsync"/>

- <int value="46" label="pidns, netns, seccomp-bpf, seccomp-tsync"/>

- <int value="47" label="suid, pidns, netns, seccomp-bpf, seccomp-tsync"/>

- <int value="48" label="yama, seccomp-tsync"/>

- <int value="49" label="suid, yama, seccomp-tsync"/>

- <int value="50" label="pidns, yama, seccomp-tsync"/>

- <int value="51" label="suid, pidns, yama, seccomp-tsync"/>

- <int value="52" label="netns, yama, seccomp-tsync"/>

- <int value="53" label="suid, netns, yama, seccomp-tsync"/>

- <int value="54" label="pidns, netns, yama, seccomp-tsync"/>

- <int value="55" label="suid, pidns, netns, yama, seccomp-tsync"/>

- <int value="56" label="seccomp-bpf, yama, seccomp-tsync"/>

- <int value="57" label="suid, seccomp-bpf, yama, seccomp-tsync"/>

- <int value="58" label="pidns, seccomp-bpf, yama, seccomp-tsync"/>

- <int value="59" label="suid, pidns, seccomp-bpf, yama, seccomp-tsync"/>

- <int value="60" label="netns, seccomp-bpf, yama, seccomp-tsync"/>

- <int value="61" label="suid, netns, seccomp-bpf, yama, seccomp-tsync"/>

- <int value="62" label="pidns, netns, seccomp-bpf, yama, seccomp-tsync"/>

- <int value="63" label="suid, pidns, netns, seccomp-bpf, yama, seccomp-tsync"/>

- <int value="64" label="userns"/>

- <int value="65" label="suid, userns"/>

- <int value="66" label="userns, pidns"/>

- <int value="67" label="suid, userns, pidns"/>

- <int value="68" label="userns, netns"/>

- <int value="69" label="suid, userns, netns"/>

- <int value="70" label="userns, pidns, netns"/>

- <int value="71" label="suid, userns, pidns, netns"/>

- <int value="72" label="userns, seccomp-bpf"/>

- <int value="73" label="suid, userns, seccomp-bpf"/>

- <int value="74" label="userns, pidns, seccomp-bpf"/>

- <int value="75" label="suid, userns, pidns, seccomp-bpf"/>

- <int value="76" label="userns, netns, seccomp-bpf"/>

- <int value="77" label="suid, userns, netns, seccomp-bpf"/>

- <int value="78" label="userns, pidns, netns, seccomp-bpf"/>

- <int value="79" label="suid, userns, pidns, netns, seccomp-bpf"/>

- <int value="80" label="userns, yama"/>

- <int value="81" label="suid, userns, yama"/>

- <int value="82" label="userns, pidns, yama"/>

- <int value="83" label="suid, userns, pidns, yama"/>

- <int value="84" label="userns, netns, yama"/>

- <int value="85" label="suid, userns, netns, yama"/>

- <int value="86" label="userns, pidns, netns, yama"/>

- <int value="87" label="suid, userns, pidns, netns, yama"/>

- <int value="88" label="userns, seccomp-bpf, yama"/>

- <int value="89" label="suid, userns, seccomp-bpf, yama"/>

- <int value="90" label="userns, pidns, seccomp-bpf, yama"/>

- <int value="91" label="suid, userns, pidns, seccomp-bpf, yama"/>

- <int value="92" label="userns, netns, seccomp-bpf, yama"/>

- <int value="93" label="suid, userns, netns, seccomp-bpf, yama"/>

- <int value="94" label="userns, pidns, netns, seccomp-bpf, yama"/>

- <int value="95" label="suid, userns, pidns, netns, seccomp-bpf, yama"/>

- <int value="96" label="userns, seccomp-tsync"/>

- <int value="97" label="suid, userns, seccomp-tsync"/>

- <int value="98" label="userns, pidns, seccomp-tsync"/>

- <int value="99" label="suid, userns, pidns, seccomp-tsync"/>

- <int value="100" label="userns, netns, seccomp-tsync"/>

- <int value="101" label="suid, userns, netns, seccomp-tsync"/>

- <int value="102" label="userns, pidns, netns, seccomp-tsync"/>

- <int value="103" label="suid, userns, pidns, netns, seccomp-tsync"/>

- <int value="104" label="userns, seccomp-bpf, seccomp-tsync"/>

- <int value="105" label="suid, userns, seccomp-bpf, seccomp-tsync"/>

- <int value="106" label="userns, pidns, seccomp-bpf, seccomp-tsync"/>

- <int value="107" label="suid, userns, pidns, seccomp-bpf, seccomp-tsync"/>

- <int value="108" label="userns, netns, seccomp-bpf, seccomp-tsync"/>

- <int value="109" label="suid, userns, netns, seccomp-bpf, seccomp-tsync"/>

- <int value="110" label="userns, pidns, netns, seccomp-bpf, seccomp-tsync"/>

- <int value="111"

- label="suid, userns, pidns, netns, seccomp-bpf, seccomp-tsync"/>

- <int value="112" label="userns, yama, seccomp-tsync"/>

- <int value="113" label="suid, userns, yama, seccomp-tsync"/>

- <int value="114" label="userns, pidns, yama, seccomp-tsync"/>

- <int value="115" label="suid, userns, pidns, yama, seccomp-tsync"/>

- <int value="116" label="userns, netns, yama, seccomp-tsync"/>

- <int value="117" label="suid, userns, netns, yama, seccomp-tsync"/>

- <int value="118" label="userns, pidns, netns, yama, seccomp-tsync"/>

- <int value="119" label="suid, userns, pidns, netns, yama, seccomp-tsync"/>

- <int value="120" label="userns, seccomp-bpf, yama, seccomp-tsync"/>

- <int value="121" label="suid, userns, seccomp-bpf, yama, seccomp-tsync"/>

- <int value="122" label="userns, pidns, seccomp-bpf, yama, seccomp-tsync"/>

- <int value="123"

- label="suid, userns, pidns, seccomp-bpf, yama, seccomp-tsync"/>

- <int value="124" label="userns, netns, seccomp-bpf, yama, seccomp-tsync"/>

- <int value="125"

- label="suid, userns, netns, seccomp-bpf, yama, seccomp-tsync"/>

- <int value="126"

- label="userns, pidns, netns, seccomp-bpf, yama, seccomp-tsync"/>

- <int value="127"

- label="suid, userns, pidns, netns, seccomp-bpf, yama, seccomp-tsync"/>

- <int value="2147483648" label="Invalid"/>

</enum>

@@ -52554,7 +51539,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="-2083195884" label="enable-firewall-hole-punching"/>

@@ -52585,7 +51569,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="-1832575380" label="show-saved-copy"/>

@@ -52601,7 +51584,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="-1630419335" label="enable-download-notification"/>

@@ -52609,18 +51591,14 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="-1514943439" label="ash-enable-swipe-to-close-in-overview-mode"/>

- <int value="-1490298774" label="enable-captive-portal-bypass-proxy-option"/>

- <int value="-1433719718" label="enable-webrtc-stun-origin"/>

- <int value="-1409643943" label="enable-child-account-detection"/>

@@ -52641,7 +51619,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="-1203742042" label="enable-gesture-selection"/>

@@ -52717,7 +51694,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="-311148335" label="v8-pac-mojo-out-of-process"/>

@@ -52738,7 +51714,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="-55944747" label="disable-child-account-detection"/>

@@ -52752,7 +51727,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="75747474" label="disable-webview-signin-flow"/>

@@ -52770,7 +51744,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="368854020" label="ash-screen-rotation-animation"/>

@@ -52825,8 +51798,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="1019857902"

- label="disable-hide-inactive-stacked-tab-close-buttons"/>

@@ -52866,7 +51837,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="1359972809" label="enable-gesture-deletion"/>

@@ -52897,7 +51867,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="1622131033" label="ozone-test-single-overlay-support"/>

@@ -52930,7 +51899,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="1944156526" label="sync-url"/>

@@ -53877,19 +52845,6 @@ To add a new entry, add it with any value and run test to compute valid value.

</enum>

-<enum name="MobileFreSignInChoice" type="int">

- <summary>

- These values are defined inside the MobileFreSignInChoice enum

- chrome/browser/android/metrics/uma_bridge.cc and reference possible ways of

- completing the sign-in part of the First Run Experience.

- </summary>

- <int value="0" label="Accept default account"/>

- <int value="1" label="Accept another account"/>

- <int value="2" label="Settings default account"/>

- <int value="3" label="Settings another account"/>

- <int value="4" label="No thanks"/>

-</enum>

@@ -54421,14 +53376,11 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="4" label="Show Saved Copy Button Shown"/>

- <int value="5" label="Show Saved Copy Button Clicked"/>

- <int value="6" label="Show Saved Copy Button Click Load Error"/>

+ <int value="4" label="Load Stale Button Shown"/>

+ <int value="5" label="Load Stale Button Clicked"/>

+ <int value="6" label="Load Stale Button Click Load Error"/>

- <int value="9" label="Both Buttons Shown"/>

- <int value="10" label="Both Buttons Shown, Show Saved Copy Clicked"/>

- <int value="11" label="Both Buttons Shown, Reload Clicked"/>

</enum>

@@ -55206,10 +54158,6 @@ To add a new entry, add it with any value and run test to compute valid value.

Whitelisted exception for bug 316759. Suspect background address detection,

field unknown.

</int>

- <int value="5" label="EXCEPTION_NSREGULAREXPRESSION_NIL_STRING">

- Whitelisted exception for bug 466076. Suspect background address detection,

- field unknown.

- </int>

</enum>

@@ -55473,7 +54421,6 @@ To add a new entry, add it with any value and run test to compute valid value.

label="Opened automatically / Confirming generated password saved"/>

<int value="5"

label="Opened automatically / Offering a credential to choose"/>

- <int value="6" label="Opened automatically / Auto-signin toast"/>

</enum>

@@ -55955,7 +54902,8 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="9" label="Auto-signin toast timeout"/>

+ <int value="9" label="Clicked collect URL"/>

+ <int value="10" label="Clicked do not collect URL"/>

</enum>

@@ -55971,13 +54919,10 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="10714106" label="PPB_OutputProtection_Private;0.1"/>

- <int value="11143977" label="PPB_PlatformVerification_Private;0.2"/>

- <int value="36133501" label="PPB_MediaStreamVideoTrack;1.0"/>

@@ -55998,7 +54943,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="344923193" label="PPB_CompositorLayer;0.2"/>

@@ -56006,7 +54950,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="596770967" label="PPB_X509Certificate_Private;0.1"/>

@@ -56020,9 +54963,7 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="732838108" label="PPB_IsolatedFileSystem_Private;0.2"/>

- <int value="760246876" label="PPB_OpenGLES2VertexArrayObject;1.0"/>

@@ -56034,16 +54975,13 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="866907383" label="PPB_View;1.2"/>

- <int value="906618937" label="PPB_Find_Private;0.3"/>

- <int value="929640141" label="PPB_VideoDestination_Private;0.1"/>

@@ -56077,10 +55015,8 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="1262834677" label="PPB_CameraDevice_Private;0.1"/>

- <int value="1304992407" label="PPB_UDPSocket;1.2"/>

@@ -56094,7 +55030,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="1502481774" label="PPB_OpenGLES2ChromiumMapSub(Dev);1.0"/>

@@ -56102,7 +55037,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="1616589391" label="PPB_TCPServerSocket_Private;0.2"/>

@@ -56110,7 +55044,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="1714657156" label="PPB_MediaStreamAudioTrack;0.1"/>

@@ -56119,20 +55052,15 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="1827038364" label="PPB_DisplayColorProfile_Private;0.1"/>

- <int value="1845295664" label="PPB_Ext_CrxFileSystem_Private;0.1"/>

- <int value="1955790313" label="PPB_MediaStreamVideoTrack;0.1"/>

- <int value="1970082102" label="PPB_TCPServerSocket_Private;0.1"/>

- <int value="1997668256" label="PPB_GLESChromiumTextureMapping(Dev);0.1"/>

@@ -56289,13 +55217,6 @@ To add a new entry, add it with any value and run test to compute valid value.

</enum>

-<enum name="PluginPowerSaverPosterParamPresence" type="int">

- <int value="0" label="No poster param. Plugin power saver disabled."/>

- <int value="1" label="No poster param. Plugin power saver enabled."/>

- <int value="2" label="Poster param exists. Plugin power saver disabled."/>

- <int value="3" label="Poster param exists. Plugin power saver enabled."/>

-</enum>

@@ -56817,7 +55738,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="10" label="PRINT_WITH_EXTENSION"/>

</enum>

@@ -57447,47 +56367,16 @@ To add a new entry, add it with any value and run test to compute valid value.

</enum>

-<enum name="PushDeliveryStatus" type="int">

- <int value="0" label="Successful"/>

- <int value="1" label="Message was invalid"/>

- <int value="2" label="App id was unknown"/>

- <int value="3" label="App no longer has permission"/>

- <int value="4" label="Service Worker not found"/>

- <int value="5" label="Service Worker error"/>

- <int value="6" label="event.waitUntil promise rejected"/>

-</enum>

-<enum name="PushGetRegistrationStatus" type="int">

- <int value="0" label="Successful"/>

- <int value="1" label="No push service"/>

- <int value="2" label="Storage error"/>

- <int value="3" label="Registration not found"/>

- <int value="4" label="Registration not found (no incognito push service)"/>

-</enum>

- <int value="1" label="Service Worker not found"/>

- <int value="2" label="No push service"/>

+ <int value="1" label="Page has no active Service Worker"/>

+ <int value="2" label="Push service not available"/>

- <int value="9" label="Network error"/>

- <int value="10" label="Permission denied (no incognito push service)"/>

-</enum>

-<enum name="PushUnregistrationStatus" type="int">

- <int value="0" label="Successful - from push service"/>

- <int value="1" label="Successful - was not registered"/>

- <int value="2" label="Pending - will retry network error"/>

- <int value="3" label="Service Worker not found"/>

- <int value="4" label="No push service"/>

- <int value="5" label="Pending - will retry push service error"/>

- <int value="6" label="Storage error"/>

- <int value="7" label="Network error"/>

</enum>

@@ -57875,7 +56764,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="61" label="IDC_CONTENT_CONTEXT_OPENORIGINALIMAGENEWTAB"/>

</enum>

@@ -58057,41 +56945,33 @@ To add a new entry, add it with any value and run test to compute valid value.

</enum>

- <int value="0" label="FAILURE_DATABASE_CORRUPT"/>

- <int value="1" label="FAILURE_DATABASE_CORRUPT_HANDLER"/>

- <int value="2" label="FAILURE_BROWSE_DATABASE_UPDATE_BEGIN"/>

- <int value="3" label="FAILURE_BROWSE_DATABASE_UPDATE_FINISH"/>

- <int value="4" label="FAILURE_DATABASE_FILTER_MISSING_OBSOLETE"/>

- <int value="5" label="FAILURE_DATABASE_FILTER_READ_OBSOLETE"/>

- <int value="6" label="FAILURE_DATABASE_FILTER_WRITE_OBSOLETE"/>

- <int value="7" label="FAILURE_DATABASE_FILTER_DELETE"/>

- <int value="8" label="FAILURE_DATABASE_STORE_MISSING"/>

- <int value="9" label="FAILURE_DATABASE_STORE_DELETE"/>

- <int value="10" label="FAILURE_DOWNLOAD_DATABASE_UPDATE_BEGIN"/>

- <int value="11" label="FAILURE_DOWNLOAD_DATABASE_UPDATE_FINISH"/>

- <int value="12" label="FAILURE_WHITELIST_DATABASE_UPDATE_BEGIN"/>

- <int value="13" label="FAILURE_WHITELIST_DATABASE_UPDATE_FINISH"/>

- <int value="14" label="FAILURE_BROWSE_PREFIX_SET_READ"/>

- <int value="15" label="FAILURE_BROWSE_PREFIX_SET_WRITE"/>

- <int value="16" label="FAILURE_BROWSE_PREFIX_SET_DELETE"/>

- <int value="17" label="FAILURE_EXTENSION_BLACKLIST_UPDATE_BEGIN"/>

- <int value="18" label="FAILURE_EXTENSION_BLACKLIST_UPDATE_FINISH"/>

- <int value="19" label="FAILURE_EXTENSION_BLACKLIST_DELETE"/>

- <int value="20" label="FAILURE_SIDE_EFFECT_FREE_WHITELIST_UPDATE_BEGIN"/>

- <int value="21" label="FAILURE_SIDE_EFFECT_FREE_WHITELIST_UPDATE_FINISH"/>

- <int value="22" label="FAILURE_SIDE_EFFECT_FREE_WHITELIST_DELETE"/>

- <int value="23" label="FAILURE_SIDE_EFFECT_FREE_WHITELIST_PREFIX_SET_READ"/>

- <int value="24" label="FAILURE_SIDE_EFFECT_FREE_WHITELIST_PREFIX_SET_WRITE"/>

- <int value="25" label="FAILURE_SIDE_EFFECT_FREE_WHITELIST_PREFIX_SET_DELETE"/>

- <int value="26" label="FAILURE_IP_BLACKLIST_UPDATE_BEGIN"/>

- <int value="27" label="FAILURE_IP_BLACKLIST_UPDATE_FINISH"/>

- <int value="28" label="FAILURE_IP_BLACKLIST_UPDATE_INVALID"/>

- <int value="29" label="FAILURE_IP_BLACKLIST_DELETE"/>

- <int value="30" label="FAILURE_UNWANTED_SOFTWARE_DATABASE_UPDATE_BEGIN"/>

- <int value="31" label="FAILURE_UNWANTED_SOFTWARE_DATABASE_UPDATE_FINISH"/>

- <int value="32" label="FAILURE_UNWANTED_SOFTWARE_PREFIX_SET_READ"/>

- <int value="33" label="FAILURE_UNWANTED_SOFTWARE_PREFIX_SET_WRITE"/>

- <int value="34" label="FAILURE_UNWANTED_SOFTWARE_PREFIX_SET_DELETE"/>

+ <int value="0" label="CORRUPT"/>

+ <int value="1" label="CORRUPT_HANDLER"/>

+ <int value="2" label="BROWSE_DB_UPDATE_BEGIN"/>

+ <int value="3" label="BROWSE_DB_UPDATE_FINISH"/>

+ <int value="4" label="FILTER_MISSING"/>

+ <int value="5" label="FILTER_READ"/>

+ <int value="6" label="FILTER_WRITE"/>

+ <int value="7" label="FILTER_DELETE"/>

+ <int value="8" label="STORE_MISSING"/>

+ <int value="9" label="STORE_DELETE"/>

+ <int value="10" label="DOWNLOAD_DB_UPDATE_BEGIN"/>

+ <int value="11" label="DOWNLOAD_DB_UPDATE_FINISH"/>

+ <int value="12" label="CSD_DB_UPDATE_BEGIN"/>

+ <int value="13" label="CSD_DB_UPDATE_FINISH"/>

+ <int value="14" label="BROWSE_PREFIX_SET_MISSING"/>

+ <int value="15" label="BROWSE_PREFIX_SET_READ"/>

+ <int value="16" label="BROWSE_PREFIX_SET_WRITE"/>

+ <int value="17" label="BROWSE_PREFIX_SET_DELETE"/>

+ <int value="18" label="EXTENSION_BLACKLIST_UPDATE_BEGIN"/>

+ <int value="19" label="EXTENSION_BLACKLIST_UPDATE_FINISH"/>

+ <int value="20" label="EXTENSION_BLACKLIST_UPDATE_DELETE"/>

+ <int value="21" label="SIDE_EFFECT_FREE_WHITELIST_UPDATE_BEGIN"/>

+ <int value="22" label="SIDE_EFFECT_FREE_WHITELIST_UPDATE_FINISH"/>

+ <int value="23" label="SIDE_EFFECT_FREE_WHITELIST_DELETE"/>

+ <int value="24" label="SIDE_EFFECT_FREE_WHITELIST_PREFIX_SET_READ"/>

+ <int value="25" label="SIDE_EFFECT_FREE_WHITELIST_PREFIX_SET_WRITE"/>

+ <int value="26" label="SIDE_EFFECT_FREE_WHITELIST_PREFIX_SET_DELETE"/>

</enum>

@@ -58377,23 +57257,10 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="5" label="ADD_RESPONSE_TRIGGERRED"/>

+ <int value="5" label="ADDED"/>

- <int value="9" label="ADD_PERSISTENCE_TRIGGERRED"/>

- <int value="10" label="UNLOAD_FOR_DESTRUCTION"/>

-</enum>

-<enum name="SdchPersistenceFailureReason" type="int">

- <summary>

- Errors that can occur when reading in or writing out persisted dictionary

- information. See enum PersistenceFailureReason in net/sdch/sdch_owner.cc for

- more information.

- </summary>

- <int value="1" label="NO_FILE"/>

- <int value="2" label="READ_FAILED"/>

- <int value="3" label="WRITE_FAILED"/>

</enum>

@@ -58626,24 +57493,6 @@ To add a new entry, add it with any value and run test to compute valid value.

</enum>

-<enum name="ServiceWorkerStatusCode" type="int">

- <int value="0" label="SERVICE_WORKER_OK"/>

- <int value="1" label="SERVICE_WORKER_ERROR_FAILED"/>

- <int value="2" label="SERVICE_WORKER_ERROR_ABORT"/>

- <int value="3" label="SERVICE_WORKER_ERROR_START_WORKER_FAILED"/>

- <int value="4" label="SERVICE_WORKER_ERROR_PROCESS_NOT_FOUND"/>

- <int value="5" label="SERVICE_WORKER_ERROR_NOT_FOUND"/>

- <int value="6" label="SERVICE_WORKER_ERROR_EXISTS"/>

- <int value="7" label="SERVICE_WORKER_ERROR_INSTALL_WORKER_FAILED"/>

- <int value="8" label="SERVICE_WORKER_ERROR_ACTIVATE_WORKER_FAILED"/>

- <int value="9" label="SERVICE_WORKER_ERROR_IPC_FAILED"/>

- <int value="10" label="SERVICE_WORKER_ERROR_NETWORK"/>

- <int value="11" label="SERVICE_WORKER_ERROR_SECURITY"/>

- <int value="12" label="SERVICE_WORKER_ERROR_EVENT_WAITUNTIL_REJECTED"/>

- <int value="13" label="SERVICE_WORKER_ERROR_STATE"/>

- <int value="14" label="SERVICE_WORKER_ERROR_TIMEOUT"/>

-</enum>

@@ -59412,7 +58261,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="3" label="Fell back to download page"/>

</enum>

@@ -59864,16 +58712,6 @@ To add a new entry, add it with any value and run test to compute valid value.

</enum>

-<enum name="SSLOrQUICVersion" type="int">

- <int value="0" label="Unknown"/>

- <int value="1" label="SSL 2.0"/>

- <int value="2" label="SSL 3.0"/>

- <int value="3" label="TLS 1.0"/>

- <int value="4" label="TLS 1.1"/>

- <int value="5" label="TLS 1.2"/>

- <int value="7" label="QUIC"/>

-</enum>

@@ -60145,7 +58983,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="7" label="Begin SRT download"/>

</enum>

@@ -60623,12 +59460,6 @@ To add a new entry, add it with any value and run test to compute valid value.

</enum>

-<enum name="UmaEntropySourceType" type="int">

- <int value="0" label="No entropy source (never hit)"/>

- <int value="1" label="Low Entropy Source"/>

- <int value="2" label="High Entropy Source"/>

-</enum>

@@ -61005,7 +59836,6 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="11" label="YV12HD"/>

</enum>

@@ -61125,9 +59955,8 @@ To add a new entry, add it with any value and run test to compute valid value.

- <int value="3" label="Unsupported Stream Parameters"/>

+ <int value="3" label="Unsupported Stream"/>

- <int value="5" label="Unsupported Stream"/>

</enum>

@@ -61822,12 +60651,6 @@ To add a new entry, add it with any value and run test to compute valid value.

<affected-histogram name="PLT.LoadType"/>

</histogram_suffixes>

-<histogram_suffixes name="CreditCardScanSuccess">

- <suffix name="Completed" label="Credit card scan completed."/>

- <suffix name="Cancelled" label="Credit card scan was cancelled."/>

- <affected-histogram name="Autofill.ScanCreditCard.Duration"/>

-</histogram_suffixes>

<histogram_suffixes name="CrosFirstRunStep" separator="">

@@ -61898,28 +60721,6 @@ To add a new entry, add it with any value and run test to compute valid value.

<suffix name="ContentLength_Image_WEBP"

label="for each carrier, number of WebP image responses whose

Content-Length header has been tampered with"/>

- <suffix name="CompressionRatio_Image"

- label="the histogram of compression ratio of images"/>

- <suffix name="CompressionRatio_Image_GIF"

- label="the histogram of compression ratio of GIF images"/>

- <suffix name="CompressionRatio_Image_JPG"

- label="the histogram of compression ratio of JPG images"/>

- <suffix name="CompressionRatio_Image_PNG"

- label="the histogram of compression ratio of PNG images"/>

- <suffix name="CompressionRatio_Image_WEBP"

- label="the histogram of compression ratio of WEBP images"/>

- <suffix name="CompressionRatio_Image_0_10KB"

- label="the histogram of compression ratio of images whose sizes are in

- the range of 0-10KB"/>

- <suffix name="CompressionRatio_Image_10_100KB"

- label="the histogram of compression ratio of images whose sizes are in

- the range of 10-100KB"/>

- <suffix name="CompressionRatio_Image_100_500KB"

- label="the histogram of compression ratio of images whose sizes are in

- the range of 100-500KB"/>

- <suffix name="CompressionRatio_Image_500KB"

- label="the histogram of compression ratio of images whose sizes are

- larger than 500KB"/>

<suffix name="ContentLength_JS"

label="for each carrier, number of JavaScript responses whose

Content-Length header has been tampered with"/>

@@ -62210,11 +61011,8 @@ To add a new entry, add it with any value and run test to compute valid value.

- <suffix name="HungBrowserTerminated"/>

- <suffix name="ProcessSingletonIsShuttingDown"/>

- <suffix name="RendezvousToHungBrowser"/>

« components/autofill/core/browser/autofill_metrics.cc ('K') | « components/autofill/core/browser/autofill_metrics.cc ('k') | no next file » | no next file with comments »