kerenzhu@chromium.org dayeung@chromium.org yuhengh@chromium.org tluk@chromium.org robliao@chromium.org Records the reason a bubble was closed. yuhengh@chromium.org kerenzhu@chromium.org dayeung@chromium.org tluk@chromium.org robliao@chromium.org Records the time it takes from a bubble construction to when the compositor finishes the first presentation. yuhengh@chromium.org kerenzhu@chromium.org dayeung@chromium.org tluk@chromium.org robliao@chromium.org Records the time it takes from a bubble construction to when the bubble becomes visible. yuhengh@chromium.org kerenzhu@chromium.org dayeung@chromium.org tluk@chromium.org robliao@chromium.org Records the time a bubble is visible. benwgold@google.com lens-chrome@google.com Whether the user supports the Lens intent and if not, the reason why. Recorded only if the feature is enabled when the long-press context menu is shown for an image. twellington@chromium.org clank-app-team@google.com {Type} The option that the user selected from a context menu on Android. This is logged on Android only; check out ContextMenu.SelectedOptionIOS for iOS, and ContextMenu.SelectedOptionDesktop for desktop. Note that if a menu is invoked on mixed content, only one of the submetrics receives the log; read the code to determine which one. avi@chromium.org mpearson@chromium.org The option that the user selected from a context menu on desktop. This is logged on desktop only; check out ContextMenu.SelectedOptionIOS for iOS, and ContextMenu.SelectedOptionAndroid for Android. Note that if a menu is invoked on mixed content, only one of the submetrics receives the log; read the code to determine which one. {ContextMenuTypeDesktop} mpearson@chromium.org twellington@chromium.org clank-app-team@google.com {Type} Recorded when a context menu is shown, sliced by whether a web contents was present. (It generally should be; indeed, this code path should not be followed when it is absent. For instance, invoking a context menu from the new tab page or from the sad tab page will not cause an emission to this histogram.) Note that this refers to link context menus, not the cut-copy-paste context menus that can appear during long presses on text on a web page or long presses in the omnibox. This is an Android-only metric; compare with RenderViewContextMenu.Shown and RenderViewContextMenu.Used on desktop. jeffreycohen@chromium.org chrome-shared-highlighting@google.com Records how long it takes to press on "Share" from the time context menu is shown. Android only. yyushkina@chromium.org Number of times the emoji item in the views text services context menu is used. grt@chromium.org catan-team@chromium.org A .pak file was prevented from being opened because it was in use, and this error persisted for at least 300ms. Recorded once for each attempt to open a .pak file that fails due to FILE_ERROR_IN_USE. grt@chromium.org catan-team@chromium.org The number of retries (not counting the initial attempt) required to open a .pak file that could not initially be opened because it was in use. Recorded once for each successfully opened .pak file after an initial FILE_ERROR_IN_USE. agale@chromium.org robliao@chromium.org Times the default browser info bar has been shown before the user accepted the prompt. pmonette@chromium.org robliao@chromium.org Possible user interactions with the default browser info bar. jessemckenna@google.com davidbienvenu@chromium.org User interaction with the pin-to-taskbar infobar (e.g., accepted, ignored, dismissed). gab@chromium.org pmonette@chromium.org Whether Chrome was the default browser when it started up. Only logged correctly on Windows and Mac. Logged incorrectly on other platforms. On Linux, this histogram is no longer logged as of 2021/10/18 due to browser test hangs. See crbug.com/1216328. For ChromeOS, no histogram is necessary because Chrome is always the default browser. For Android, see Mobile.DefaultBrowser.State. For iOS, in the future Chrome will be allowed to be the default browser. How that will be logged is to be decided at the time of writing this description. alsan@chromium.org atharvmaan@chromium.org koretadaniel@chromium.org Time between starting the search for the Windows Settings default-apps window and the window being discovered by the visual guided setter. Recorded on Windows only, when the window is found. alsan@chromium.org atharvmaan@chromium.org koretadaniel@chromium.org Outcome of the visual guided setter flow that docks the Windows Settings default-apps window over the chrome://default-browser WebUI stage. Recorded on Windows only, when the flow tears down. alsan@chromium.org atharvmaan@chromium.org koretadaniel@chromium.org chrome-desktop-ui-waterloo@google.com Recorded when the primary setter fails (e.g. times out). Records whether Chrome eventually becomes the default browser asynchronously from {DefaultBrowserEntrypointType} with {DefaultBrowserSetterType} as the setter. alsan@chromium.org atharvmaan@chromium.org koretadaniel@chromium.org chrome-desktop-ui-waterloo@google.com Records the action taken by user when presented with an option to set Chrome as the default browser from {DefaultBrowserEntrypointType} with {DefaultBrowserSetterType} as the setter. alsan@chromium.org atharvmaan@chromium.org koretadaniel@chromium.org chrome-desktop-ui-waterloo@google.com Records how many times {DefaultBrowserEntrypointType} entrypoint with {DefaultBrowserSetterType} as the setter was shown to the user. alsan@chromium.org atharvmaan@chromium.org koretadaniel@chromium.org chrome-desktop-ui-waterloo@google.com Recorded when the primary setter fails (e.g. times out) but Chrome eventually becomes the default browser asynchronously. Records the duration from when the setter failed until Chrome becomes the default browser from {DefaultBrowserEntrypointType} with {DefaultBrowserSetterType} as the setter. alsan@chromium.org atharvmaan@chromium.org koretadaniel@chromium.org chrome-desktop-ui-waterloo@google.com Records whether setting Chrome as the default browser was successful using {DefaultBrowserSetterType}. alsan@chromium.org atharvmaan@chromium.org koretadaniel@chromium.org chrome-desktop-ui-waterloo@google.com Only recorded when setting Chrome as the default browser succeeds synchronously (within the setter's timeout) after the user accepts the default browser flow using {DefaultBrowserSetterType}. alsan@chromium.org atharvmaan@chromium.org koretadaniel@chromium.org chrome-desktop-ui-waterloo@google.com Only logged on Windows. Logs a comparison of the default browser state check result using the standard Win API compared to {DefaultBrowserStateValidator}. Results are relative to the Win API checker; e.g., a false-positive means the Win API detected the default browser but the alternative validator did not. mych@chromium.org chrome-webium-product-eng@google.com Deprecated. Replaced by WithExistingWindow and WithoutExistingWindow variants. Records the time from immediately before the Browser constructor is called to 'First Paint' of the new browser window. Aggregated across all sources. mych@chromium.org chrome-webium-product-eng@google.com Deprecated. Replaced by WithExistingWindow and WithoutExistingWindow variants. Records the time from immediately before the Browser constructor is called to first paint of the Reload Button in the new browser window. Aggregated across all sources. annasato@chromium.org chrome-webium-product-eng@google.com Records the duration from window creation to closing the browser window for new windows {CreationSource} {ExistingWindow} {Version}. This is only recorded for desktop platforms when the InitialWebUIMetrics is enabled, and when the initial paint has not been recorded. mych@chromium.org chrome-webium-product-eng@google.com Records the time from {StartPoint} to 'First Paint' of the new browser window. {CreationSource} {ExistingWindow} {Version}. This is only recorded for desktop platforms when the InitialWebUIMetrics is enabled. mych@chromium.org chrome-webium-product-eng@google.com Records the duration from the initial show/activation request of a new browser window to its first paint. {CreationSource} {ExistingWindow} {Version}. This metric is used to measure the impact of window show deferral. It is recorded only once per window lifecycle. If multiple windows are shown during startup, e.g. due to session restore, the first window is measured in "InitialWebUI.Startup" and not in this histogram. This is only recorded for desktop platforms when the InitialWebUIMetrics is enabled. mych@chromium.org chrome-webium-product-eng@google.com Records the delay between the native browser window's first presentation (paint) and the Reload Button first paint in a new window. {CreationSource} {ExistingWindow} {Version}. This is a direct, session-linked measurement of the delta, unlike the separately logged `.FirstPaint` metrics. Used to quantify the rendering lag. This is only recorded for desktop platforms when the InitialWebUIMetrics is enabled. mych@chromium.org chrome-webium-product-eng@google.com Records the time from {StartPoint} to first {PaintType} of the Reload Button in the new browser window. {CreationSource} {ExistingWindow} {Version}. This is only recorded for desktop platforms when the InitialWebUIMetrics is enabled. leimy@chromium.org chrome-webium-product-eng@google.com Records the time from navigation start to {PaintType} for the Reload Button when the InitialWebUIWindowMetricsManager was null and the metric was dropped. Note: This is measured from NavigationStart rather than FromConstructor because the browser window creation timestamp is unavailable when the metrics manager is null (e.g. for background prewarmed WebContents whose paint occurs before a window constructor runs, or fast in-process loads before the window reference is resolved). mych@chromium.org chrome-webium-product-eng@google.com Counts the number of times the ReloadButton is activated, sliced by input type. This is only recorded for desktop platforms when the InitialWebUIMetrics is enabled. mych@chromium.org chrome-webium-product-eng@google.com Records the latency from {InputType} user interaction with the WebUI or C++ Views reload button to the initiation of the reload command execution. For C++ Views, the start time is the event timestamp of the click or key press, and the end time is when the browser button handler is executed. The metric is emitted immediately during the button press handler. For WebUI, the start time is the physical interaction time reconstructed in the browser process by adding the renderer-reported interaction time offset (relative to navigation start) to the browser-side recorded navigation start ticks. The end time is when the browser process receives the Mojo reload request. The metric is emitted immediately upon validating and processing the Mojo request. This is only recorded for desktop platforms when the InitialWebUIMetrics is enabled. mych@chromium.org chrome-webium-product-eng@google.com Deprecated. Removed the WithExistingWindow and WithoutExistingWindow dimension from Startup metrics, since they do not apply during startup. Records the time from browser application startup to the first presentation of the browser window onto the screen when no existing window is present. mych@chromium.org chrome-webium-product-eng@google.com Deprecated. Removed the WithExistingWindow and WithoutExistingWindow dimension from Startup metrics, since they do not apply during startup. Records the delay between the native browser window's first presentation (paint) and the Reload Button first paint during startup when no existing window is present. mych@chromium.org chrome-webium-product-eng@google.com Deprecated. Removed the WithExistingWindow and WithoutExistingWindow dimension from Startup metrics, since they do not apply during startup. Records the time spent initializing a newly constructed ReloadButton in standard browser application startup. The timer starts immediately after the browser application startup, and ends immediately after a contentful paint of the view is requested when no existing window is present. mych@chromium.org chrome-webium-product-eng@google.com Deprecated. Removed the WithExistingWindow and WithoutExistingWindow dimension from Startup metrics, since they do not apply during startup. Records the time spent initializing a newly constructed ReloadButton in standard browser application startup. The timer starts immediately after the browser application startup, and ends immediately after a paint of the view is requested when no existing window is present. annasato@chromium.org chrome-webium-product-eng@google.com Records the duration from the initial show/activation request of the first browser window during {Scenario} startup to closing the window{StartupTemperature}. This is only recorded for desktop platforms when the InitialWebUIMetrics is enabled, and when the initial paint has not been recorded. mych@chromium.org chrome-webium-product-eng@google.com Records the time from {Scenario} browser application startup to the first presentation of the browser window onto the screen{StartupTemperature}. This metric is mutually exclusive by scenarios. This is only recorded for desktop platforms when the InitialWebUIMetrics feature is enabled. mych@chromium.org chrome-webium-product-eng@google.com Records the duration from the initial show/activation request of the first browser window during {Scenario} startup to its first paint{StartupTemperature}. This metric is used to measure the impact of window show deferral. It is recorded only once per browser process. If multiple windows are shown during startup, e.g. due to session restore, only the first window is measured, and all the others are measured in the "InitialWebUI.NewWindow" histogram. This is only recorded for desktop platforms when the InitialWebUIMetrics feature is enabled. mych@chromium.org chrome-webium-product-eng@google.com Records the delay between the native browser window's first presentation (paint) and the Reload Button first paint during {Scenario} startup {StartupTemperature}. This is a direct, session-linked measurement of the delta, unlike the separately logged `.FirstPaint` metrics. Used to quantify the rendering lag of the WebUI process relative to the native UI creation during heavy resource contention at startup. This metric is mutually exclusive by scenarios. This is only recorded for desktop platforms when the InitialWebUIMetrics feature is enabled. elkurin@chromium.org chrome-webium-product-eng@google.com Records the duration from the start of {Scenario} browser application startup to the point where the dedicated renderer process for the Reload button WebUI is initialized {StartupTemperature}. This metric specifically measures the renderer process creation cost (Cost A), which is an overhead incurred by the Initial WebUI architecture that does not exist in the native C++ Views implementation. This is only recorded for desktop platforms when the InitialWebUIMetrics feature is enabled. elkurin@chromium.org chrome-webium-product-eng@google.com Records the duration from the start of {Scenario} browser application startup to the point where the dedicated renderer process for the Reload button WebUI is launched {StartupTemperature}. This metrics captures the completion of the process launch sequence. Comparing this with the `.RendererProcessCreated` metric reveals the time spent in the process launch phase, specifically isolating the OS and Sandbox overhead incurred before the renderer becomes available. This is only recorded for desktop platforms when the InitialWebUIMetrics feature is enabled. mych@chromium.org chrome-webium-product-eng@google.com Records the time spent initializing a newly constructed ReloadButton in the {Scenario} browser application startup with pre/post Initial WebUI setup. The timer starts immediately after the browser application startup{StartupTemperature}, and ends immediately after a {PaintType} of the view is requested. This metric is mutually exclusive by scenarios. For FirstPaint, the paint is requested by either the browser process (pre-Initial WebUI) or by the WebUI renderer process (post-Initial WebUI). Only recorded on desktop platforms. leimy@chromium.org chrome-webium-product-eng@google.com Records the time elapsed from when the main document finishes parsing and becomes interactive (domInteractive) to when the WebUI toolbar component completes its first rendering update (firstUpdated). This measures the latency introduced by JavaScript execution and the initial Lit component lifecycle. This is only recorded for desktop platforms when the InitialWebUIMetrics feature is enabled. leimy@chromium.org chrome-webium-product-eng@google.com Recorded during `RenderProcessHostImpl::Init()` for TopChromeWebUI processes. Records true if there is already an existing RenderProcessHost for TopChromeWebUI for the same profile that is initialized and not dead. leimy@chromium.org chrome-webium-product-eng@google.com Records the status when the Web UI Toolbar render process is terminated. This is recorded every time when `WebUIToolbarWebView` receives `PrimaryMainFrameRenderProcessGone()` signal including the normal termination (i.e. `TERMINATION_STATUS_NORMAL_TERMINATION` and `TERMINATION_STATUS_STILL_RUNNING`). leimy@chromium.org chrome-webium-product-eng@google.com Record the number of times that the Web UI Toolbar render process is terminated abnormmaly and it exceeds the recovery limit. mych@chromium.org chrome-webium-product-eng@google.com Records the counts of key Initial WebUI views when they are created in the constructor. Use this to normalize other metrics. This is only recorded for desktop platforms when the InitialWebUIMetrics is enabled. dayeung@chromium.org etienneb@chromium.org Time retrieve the fallback fonts on the system used for RenderTextHarfBuzz::ShapeRuns. This metric is known to be quite slow on bad cases. dayeung@chromium.org etienneb@chromium.org Time retrieve the preferred fallback font on the system used for RenderTextHarfBuzz::ShapeRuns. Fallback font is determined based on the input text and locale. dayeung@chromium.org etienneb@chromium.org Count of missing glyphs at the end of text shaping. dayeung@chromium.org etienneb@chromium.org This metric records the fallback font mechanism required to complete the shaping of a text. dayeung@chromium.org etienneb@chromium.org Time to perform RenderTextHarfBuzz::ShapeRuns with retrieved the fallback fonts. This metric is known to be quite slow on bad cases. sophiechang@chromium.org chrome-desktop-search@google.com Recorded when the user selects the "Search Google for" (Search Web for) context menu item. Logs the number of words selected. avi@chromium.org edwardjung@chromium.org mpearson@chromium.org Count of renderer view context menu items shown. avi@chromium.org mpearson@chromium.org chrome-analysis-team@google.com Count of renderer view context menu items (Only commands now) used. Note that this counts cases where the context menu item is used, but the item has no effect (eg. autofill commands have no effect if the RenderFrameHost is null). Update: as of M122, setting text direction via the context menu may also have no effect if the RFH is null, though we will continue to count in this case. The user action RenderViewContextMenu.Used.IDC_CONTENT_CONTEXT_SEARCHWEBFOR is also logged in case that IDC_CONTENT_CONTEXT_SEARCHWEBFOR is logged to this histogram. This histogram is of special interest to the chrome-analysis-team@. Do not change its semantics or retire it without talking to them first. aishwaryarj@google.com src/chrome/browser/ui/messages/OWNERS Records the reason why a snackbar was dismissed. vpasupathy@google.com chrome-ui-security-bugs@google.com Records the combined size of the standard and persistent snackbar queues at the exact moment a new snackbar is inserted via add(). Used to detect queue spam and DoS conditions. pavely@chromium.org src/chrome/browser/ui/messages/OWNERS Records the identifier of a snackbar every time one is shown. vpasupathy@google.com chrome-ui-security-bugs@google.com Records the difference between the actual time a snackbar was dismissed due to timeout and its requested duration. Tracks the exact uptimeMillis() to detect Android UI thread stalls or deadlocks that delay security notices. Capped at 60 seconds. elainechien@chromium.org robliao@chromium.org Chrome Labs features user-facing experiments through a button in the toolbar. This metric tracks which experiment (also called lab in the context of Chrome Labs) a user selects {State} for. This histogram is emitted to when {State} is selected in the combobox of the ChromeLabs dialog. robliao@chromium.org pauljensen@chromium.org Whether the home button is enabled and overflowed due to width constraints. mych@chromium.org chrome-webui@google.com Measures the time elapsed from the initiation of a user-initiated request to its first contentful paint for a Top Chrome UI: {UIName}. This metric is recorded for both Native and WebUI implementations. To ensure comparative parity, it is recorded at most once per window instance. This aligns the native view lifecycle with the WebUI document lifecycle. Only recorded on desktop platforms. tluk@chromium.org skau@chromium.org Records the size of the ColorProviderManager cache when a new ColorProvider is generated. New entries are generated when a client requests a ColorProvider with a Key that is not in the cache. Since the cache size is capped, a distribution with too many results at the tail indicate that the cache is too small. gjc@google.com chrome-loading@google.com Records the duration of all FocusRing::RefreshLayer calls. Recorded when the focus ring's layer is refreshed. This captures fast cached cases as well as slow layer creation/destruction cases. This metric is only reported for clients with high-resolution clocks. gjc@google.com chrome-loading@google.com Records the duration of FocusRing::RefreshLayer calls that result in actual layer creation or destruction. Recorded when the focus ring's layer is refreshed and results in actual layer creation or destruction. This metric is only reported for clients with high-resolution clocks. dpranke@chromium.org elainechien@chromium.org kylixrd@chromium.org Records the number of times a view's InvalidateLayout() method is called during a Layout() call. Calling InvalidateLayout() during a layout call should never be necessary. dpranke@chromium.org elainechien@chromium.org kylixrd@chromium.org The maximum reentrant call depth seen during a view's layout. Normally this value will be one (Layout() was not reentered). But, we know Layout() is reentered sometimes in some views (where the value will be two), and want to measure how often that is. We also want to know if Layout() is ever reentered more than two deep. elainechien@chromium.org kylixrd@chromium.org pkasting@chromium.org Records excess layouts of a view that will not be visible. This includes doing more than one layout between paints, or any layouts after the final paint. While some such layouts might be unavoidable in computing layout-related properties during other operations, these mostly represent unnecessary work. The zero bucket counts cases where all the layouts we did were necessary, i.e. paints that had a single preceding layout. pkasting@chromium.org tluk@chromium.org skau@chromium.org Records the number of ColorProvider instances constructed and initialized by the ColorProviderManager following a NativeTheme update in a {Process} process. Emitted after the NotifyOnNativeThemeUpdated() event has been processed. pkasting@chromium.org tluk@chromium.org skau@chromium.org Records the time spent initializing a newly constructed ColorProvider instance in a {Process} process. The timer starts immediately before the ColorProvider is constructed and emitted immediately after initialization (i.e. all mixers are run and the ColorMap is created). pkasting@chromium.org tluk@chromium.org skau@chromium.org Records the time spent synchronously processing the the NotifyOnNativeThemeUpdated() event in a {Process} process. The timer starts as soon as the event handler is entered and emitted when code returns from the event handler. skau@chromium.org tluk@chromium.org The time in milliseconds to generate chrome://theme/colors.css and queue it to be sent to the renderer for WebUI. Does not include url parsing time. Recorded for every request for colors.css. Lower is better. Expired Jan 2024. Revived M124. dpapad@chromium.org chrome-webui@google.com URLs for which Chrome creates WebUIControllers. dschuyler@chromium.org tbuckley@chromium.org bettes@chromium.org Paths within chrome://settings visited. For evaluating popularity and priorities for chrome://settings GUI. Note that this metric used to include paths that were part of OS settings, but starting with M-81, this metric only records browser settings paths. For Android settings usage check Settings.FragmentAttached. kerenzhu@chromium.org dpapad@chromium.org chrome-webui@google.com WebUI URLs that are shown to the user. For WebUIs that don't have a WebUI object (e.g. chrome://dino), recorded on the network request. For others, recorded on commit if not preloaded. For preloaded WebUIs, recorded when WebUIContentsPreloadManager::Request() is invoked. This differs from WebUI.CreatedForUrl as it only logs WebUIs that are actually shown (i.e., a preloaded WebUI may never be shown). kerenzhu@chromium.org tluk@chromium.org robliao@chromium.org The reason of preloading a WebUI. Logged when a preloaded WebUI is created. kerenzhu@chromium.org dayeung@chromium.org elainechien@chromium.org tluk@chromium.org robliao@chromium.org The result of attempting to use a preloaded WebUI when a new Top Chrome WebUI is requested. kerenzhu@chromium.org chrome-webui-for-features@google.com Measures the time elapsed from the initiation of a WebUI request to its first contentful paint. This metric applies to the main frame documents of top-chrome WebUI pages, such as side-panel content. The request initiation is marked by the call to WebUIContentsPreloadManager::Request(). kerenzhu@chromium.org chrome-webui-for-features@google.com Measures the time elapsed from the initiation of a WebUI request to its largest contentful paint. This metric applies to the main frame documents of top-chrome WebUI pages, such as side-panel content. The request initiation is marked by the call to WebUIContentsPreloadManager::Request(). dpapad@chromium.org etienneb@chromium.org tluk@chromium.org The elapsed time for URL requests made through the WebUIURLLoaderFactory. The reported duration is the time spent in the browser process from the reception of the mojo request up to the content delivery through mojo call. tluk@chromium.org True if WebUICodeCache feature is enabled. This counts the number of times generated WebUICodeCache JS code cache is instantiated. ainslie@chromium.org edwardjung@chromium.org Number of times that each menu item is clicked. ainslie@chromium.org edwardjung@chromium.org The time a user takes to select a menu item after opening the menu.