commit | 7cd495130c6e156ef990fafd13108e669ec0f8ca | [log] [tgz] |
---|---|---|
author | Samuel Huang <huangs@chromium.org> | Fri May 30 13:59:35 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 30 13:59:35 2025 |
tree | 5a0fd71271f21e25455a21adfa57fdaa04442822 | |
parent | 396ffa37af71e04736d82d621b9c61e853d8533c [diff] |
[MVT Customization] Update / add metrics. This CL adds metrics for the Most Visited Tiles Customization features on Clank. Existing: 1. Custom tile impression (split by positions): * NewTabPage.SuggestionsImpression.custom_links 2. Custom tile click (split by positions): * NewTabPage.MostVisited.custom_links 3. Context menu item usage: Pin, unpin, edit: * User.Actions => Suggestions.ContextMenu.{PinItem,UnpinItem,EditItem}. Renames: 4. "Add new" button click: * Old: User.Actions => MostVisited_AddItem. * New: User.Actions => Suggestions.Button.AddItem. Added: 5. On-unpin snackbar "Undo" click: * User.Actions => Suggestions.SnackBar.UndoUnpinItem. 6. Drag-and-drop reordering: * User.Actions => Suggestions.Drag.ReorderItem. 7. Number of Custom Tiles on load: Take the simple approach of logging on first call of CustomLinksStore::RetrieveLinks(): * NewTabPage.FirstLoad.NumberOfCustomTiles. Bug: 420975821 Change-Id: I420bda8cbcfd740608403f09df6cb5b1c7eb9a62 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6596996 Commit-Queue: Samuel Huang <huangs@chromium.org> Reviewed-by: Calder Kitagawa <ckitagawa@chromium.org> Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/main@{#1467450}
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.