commit | e9ef251d829b7c8177d9862df677d02299aba955 | [log] [tgz] |
---|---|---|
author | Victor Hugo Vianna Silva <victorvianna@google.com> | Tue Sep 06 23:16:12 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 06 23:16:12 2022 |
tree | 21a2ed7bcc4de1961d7197efc7b69398233f3646 | |
parent | 6c05b7e8f529d1a319495614f66c26a9aa3068ba [diff] |
[M106] Add per-user-state metrics for send-tab-to-self UI Before this CL, metrics were only recorded when a device was selected for sending. Now also record when: device list shown, sign-in promo shown and no target device message shown. Also deprecate the Sharing.SendTabToSelf.NotificationStatus::Sent bucket since it's redundant with the existing metric above. https://source.chromium.org/chromium/chromium/src/+/main:components/send_tab_to_self/metrics_util.cc;l=67;drc=9a4aa67fccec134875880bfd893f0ed731c0e51b (cherry picked from commit 39a738181cbe731ff8fc7a6407ca207acb5e4647) Bug: 1295204 Change-Id: Ie29e8cf1ee2def4127c3e778bfe1fbcddc81a42a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3867811 Reviewed-by: Weilun Shi <sweilun@chromium.org> Auto-Submit: Victor Vianna <victorvianna@google.com> Commit-Queue: Weilun Shi <sweilun@chromium.org> Reviewed-by: Jeffrey Cohen <jeffreycohen@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1042396} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3876427 Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Victor Vianna <victorvianna@google.com> Cr-Commit-Position: refs/branch-heads/5249@{#328} Cr-Branched-From: 4f7bea5de862aaa52e6bde5920755a9ef9db120b-refs/heads/main@{#1036826}
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.