commit | 786d57fc01cb6d5f077ed345b2c41c0664bfbefa | [log] [tgz] |
---|---|---|
author | Nick Birnie <[email protected]> | Wed Aug 06 22:47:19 2025 |
committer | Chromium LUCI CQ <[email protected]> | Wed Aug 06 22:47:19 2025 |
tree | bdb31aa56be667adc47bff7ce8414628dd23c8a4 | |
parent | ca2b4464049660f7ee6b9bcefc16597a61fb853e [diff] |
[glic] Add metrics for GetContextFromFocusedTab errors The "Glic.Api.RequestCounts.GetContextFromFocusedTab" metric shows a high rate of "Request handling exception caught" events. This generic error makes it difficult to diagnose the underlying causes. Manual testing indicates that the "web contents changed" error is a significant contributor, especially in Live mode where users may navigate while a query is in flight. To provide better insight, this change introduces a new histogram, Glic.Api.GetContextFromFocusedTab.Error.{Mode}, which breaks down the exceptions by cause. A new enum, GlicGetContextFromFocusedTabError, is added to categorize the specific errors: - PermissionDeniedWindowNotShowing - TabNotFound - PermissionDeniedContextPermissionNotEnabled - PermissionDenied - WebContentsChanged The new metric is segmented by the last known user input mode (Text or Audio) to help differentiate behavior between interaction styles. This is achieved by tracking the last used input mode within GlicMetrics. Bug: 433328453 Change-Id: I498d834db364dcac33a074785509f3a71aed7e61 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6810456 Reviewed-by: David Pennington <[email protected]> Reviewed-by: Dan Harrington <[email protected]> Commit-Queue: Nick Birnie <[email protected]> Cr-Commit-Position: refs/heads/main@{#1497900}
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.