| commit | f5d01b5969b51bd55663f45d359b7ac5cf84e4db | [log] [tgz] |
|---|---|---|
| author | Andrzej Fiedukowicz <afie@google.com> | Tue Jan 21 17:56:26 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 21 17:56:26 2025 |
| tree | 40806ac2c12a59d04adab225475ba4b1f03b701b | |
| parent | e848f2efd2915154a67bfed5f1f01bf9be188045 [diff] |
Allow chrome://histograms selecting histogram while monitoring In crbug.com/40864008 it was discussed that selecting histogram while in monitoring mode isn't really supported because as soon as new data comes the selection gets invalidated. The only way to monitor single histogram as to select them before getting into monitoring mode. This attempts to fix that by doing the following: 1. Make `StartMonitoring` ignore the query taking the baseline of ALL the histograms even if one is preselected. This is done to allow selection change without changing a base point. 2. Make `GetDiff` not ignore the query returning only the histogram that is actually requested by a frontend page. 3. Don't force `requestHistograms` when hash selection changes during monitoring mode. This mixes monitoring data which are diff from baseline with a global histogram data. With monitoring mode the updated data will be pulled with the next fetch anyway (within 1s). 4. Link header to `#` allowing to reset selection (aka. `query`) without refreshing the whole page and therefore the baseline. This allows changing selection live and opens potential for selecting multiple histograms. There is a small risk of increased memory footprint for users doing a lot of selective monitoring as each of them will now keep the whole "baseline" set of histograms. However it seems like an extremely obscure use case and the footprint is not enormous anyway O(kB). Tested: * Updated and added new coverage to automated testing * Checked the functionality with local build on gLinux Change-Id: I8fbf6e7fc138e2639e2d5ea5dff2d48a5666075a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6175086 Reviewed-by: John Lee <johntlee@chromium.org> Commit-Queue: Andrzej Fiedukowicz <afie@google.com> Reviewed-by: Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/main@{#1409115}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.