Chromium Code Reviews| Index: tools/metrics/histograms/histograms.xml |
| diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml |
| index 690a2d7afa474d116aaf3659357c962371538868..69d63cd92b1d0a64f67038e2b54fd71fea4d3630 100644 |
| --- a/tools/metrics/histograms/histograms.xml |
| +++ b/tools/metrics/histograms/histograms.xml |
| @@ -25307,6 +25307,17 @@ Therefore, the affected-histogram name has to have at least one dot in it. |
| </summary> |
| </histogram> |
| +<histogram name="PasswordManager.EmptyUsernames.NotPairedWithNonempty"> |
|
engedy
2015/04/15 15:29:26
I think the concept of "pairing" is a bit unclear
msramek
2015/04/16 14:34:26
Sure. Naming is always the hardest.
|
| + <owner>msramek@chromium.org</owner> |
| + <owner>vasilii@chromium.org</owner> |
| + <summary> |
| + Number of password forms with empty username in the Login Database for which |
| + there isn't another password form from the same realm with a nonempty |
|
engedy
2015/04/15 15:29:26
nit: s/isn't/is not/
msramek
2015/04/16 14:34:26
Done.
|
| + username. In other words, number of password forms with empty username which |
| + we do not suspect to be reauthentication forms. |
| + </summary> |
| +</histogram> |
| + |
| <histogram name="PasswordManager.EmptyUsernames.OfferedToSave" |
| enum="PasswordManagerShowEmptyUsername"> |
| <owner>vasilii@chromium.org</owner> |