wychen@chromium.org gilmanmh@google.com The time spent on collecting the statistics of the document in the main frame. These statistics would be used as features to classify whether the page is suitable for DOM distiller. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. kojii@chromium.org tkent@chromium.org Counts the number of times each document.execCommand is executed. This doesn't count commands not supported by Blink. arichiv@chromium.org katabolism-finch@google.com Counts the number of invocations by the {Source}SpellChecker related to {Action} actions and whether they were allowed or denied. For more see: https://explainers-by-googlers.github.io/user-dictionary-leaks/ rakina@chromium.org Records how long one find-in-page task took from invocation start to end. Emitted when a find-in-page task finished running. csharrison@chromium.org japhet@chromium.org The position of the URL in the framebust UI list (desktop only) when it is clicked. Note that this UI surface is shared with the tab-under intervention, so elements in the list could come from either features. This metric will only be logged when a URL from the framebust (3p redirect) intervention is clicked. csharrison@chromium.org japhet@chromium.org The (android only) outcome of a particular framebust infobar. Recorded when the user either closes the infobar or declines the intervention by clicking the link. estade@chromium.org chrome-owp-storage@google.com Records actions that take place in IndexedDB. These stats are used for normalization in formulas. See go/chrome-indexeddb-heartbeat estade@chromium.org chrome-owp-storage@google.com Records the result of trying to delete an IndexedDB database, per the user using the IDBFactory::DeleteDatabase API. estade@chromium.org chrome-owp-storage@google.com Records the result of the FIRST attempt at opening the backing store for IndexedDB (i.e. retries are ignored). This is recorded when an API call needs to open the backing store (if it isn't already opened). API calls that can open the backing store are: IDBFactory::Open, GetDatabaseNames, GetDatabaseInfo, and DeleteDatabase. estade@chromium.org chrome-owp-storage@google.com Count of the different success and failure modes when opening an IndexedDB backing store - clean open, successful open with recovery, failed recovery, etc. Includes all hosts. estade@chromium.org chrome-owp-storage@google.com Count of the different success and failure modes when opening an IndexedDB backing store - clean open, successful open with recovery, failed recovery, etc. Only for docs.google.com. leimy@chromium.org evanstade@microsoft.com chrome-owp-storage@google.com Error classes returned by LevelDB when it failed to open a database. Warning: this histogram was expired from 2025-02-02 to 2025-12-01; data may be missing. leimy@chromium.org evanstade@microsoft.com chrome-owp-storage@google.com Errors (base::File::Error) encountered by a single LevelDBEnv method when opening an IndexedDB instance. {LevelDBBFEMethods} Warning: this histogram was expired from 2025-04-13 to 2025-12-01; data may be missing. leimy@chromium.org evanstade@microsoft.com chrome-owp-storage@google.com Types of corruption that LevelDB encounters when opening a database. Warning: this histogram was expired from 2025-06-22 to 2025-12-01; data may be missing. leimy@chromium.org evanstade@microsoft.com chrome-owp-storage@google.com LevelDBEnv methods that generated IO errors when opening a database. Warning: this histogram was expired from 2025-03-23 to 2025-12-01; data may be missing. estade@chromium.org chrome-owp-storage@google.com Records end to end duration of an IndexedDB operation. Unlike RequestDuration before it, this only records when an event is successfully dispatched to the page (whether the result is a success or error). Note this is only recorded for the first result dispatch for a given request, e.g. "upgradedneeded" but not "success" for an open request. leimy@chromium.org evanstade@microsoft.com chrome-owp-storage@google.com The time it takes for an IndexedDB transaction to commit, starting from when it starts executing tasks (when it reaches the front of the scheduling queue). Recorded after transaction commit fully completes. estade@chromium.org chrome-owp-storage@google.com The time it takes for an IndexedDB transaction to start after it's created. This is measured from the browser process. It represents the amount of time spent queued behind other tranactions (i.e. waiting for locks) and any other delays before the transaction can begin operations. estade@chromium.org chrome-owp-storage@google.com Recorded on the browser side (back end) when an IndexedDB transaction is aborted, specifically recording the reason for the abort. This can be triggered by javascript code on the renderer, errors or force closes on the backend, or by the transaction timeout timer. leszeks@chromium.org v8-runtime@google.com Reason for not streaming an async script. Warning: This histogram was expired from 2023-12-10 to 2024-03-19. Data may be missing. leszeks@chromium.org v8-runtime@google.com Whether an async script was streamed or not. leszeks@chromium.org v8-runtime@google.com Reason for not streaming a deferred script. Warning: This histogram was expired from 2023-12-10 to 2024-03-19. Data may be missing. leszeks@chromium.org v8-runtime@google.com Whether a deferred script was streamed or not. cduvall@chromium.org leszeks@chromium.org Whether waiting for the background compile for an inline script timed out on the main thread. This is recorded each time an inline script streamer is available when executing an inline script. Warning: This histogram was expired from 2023-11-12 to 2024-06-11. Data may be missing. cduvall@chromium.org leszeks@chromium.org Records the time the main thread is blocked while waiting for an inline script to finish compiling on a background thread. Recorded for each inline script that is compiled on a background thread. This histogram only records metrics on machines with high-resolution clocks. Warning: This histogram was expired from 2023-11-12 to 2024-06-11. Data may be missing. leszeks@chromium.org v8-runtime@google.com Reason for not streaming an other (not async, deferred or parser blocking) script. Warning: This histogram was expired from 2023-12-10 to 2024-03-19. Data may be missing. leszeks@chromium.org v8-runtime@google.com Whether an other (not async, deferred or parser blocking) script was streamed or not. leszeks@chromium.org v8-runtime@google.com Reason for not streaming a parsing blocking script. Warning: This histogram was expired from 2023-10-08 to 2024-03-19. Data may be missing. leszeks@chromium.org v8-runtime@google.com Whether a parsing blocking script was streamed or not. marja@chromium.org v8-runtime@google.com What type of cache metadata we retrieved for a script. Recorded when we are about to compile a script. marja@chromium.org v8-runtime@google.com What type of cache metadata we set for a script. If we set multiple metadata types for the same script, multiple samples are recorded. Recorded when we set the metadata. marja@chromium.org v8-loading@google.com chrome-intelligence-core@google.com Whether we produced / consumed compile hints (either local or crowdsourced) for a script. Recorded when a script is compiled (either via streaming or otherwise). marja@chromium.org v8-loading@google.com chrome-intelligence-core@google.com Whether we got a V8CompileHints model and whether it was good quality. marja@chromium.org v8-runtime@google.com Whether we produced the non-final or the final version of local compile hints. This can be used for approximating how often we end up not generating compile hints if we wait too long for the final compile hints generation. marja@chromium.org v8-runtime@google.com Whether there already was a code cache when we tried to set local compile hints. Recorded when we set compile hints.