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}
6 files changed
tree: 40806ac2c12a59d04adab225475ba4b1f03b701b
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. description
  71. DIR_METADATA
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. WATCHLISTS
README.md

Logo Chromium

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.