Chromium Code Reviews Chromium Code Reviews
Issue 2607413003:
Add security feature to ProvisionalSavePassword (Closed)
| Index: tools/metrics/histograms/histograms.xml |
| diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml |
| index 94ac7b1e3e03dc6258aa53fd429f47c5983a1a15..840dbe4e68a0ab8dce135fb2fef34964e8ef47e6 100644 |
| --- a/tools/metrics/histograms/histograms.xml |
| +++ b/tools/metrics/histograms/histograms.xml |
| @@ -44473,6 +44473,22 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries. |
| </summary> |
| </histogram> |
| +<histogram |
| + name="PasswordManager.ShouldBlockPasswordForSameOriginButDifferentScheme" |
| + enum="BooleanBlocked"> |
| + <owner>jdoerrie@chromium.org</owner> |
| + <summary> |
| + This metric is recorded every time Chrome detects a password form |
| + submission. The credential might be saved, or it might be blocked. It is |
|
vasilii
2017/01/12 14:59:21
Here and below: it's not saved, it's just proposed
jdoerrie
2017/01/12 17:40:58
Done.
|
| + blocked if the previously detected password form submission was successful, |
| + and the current submission is from a URL with the same origin, but a |
| + different and insecure scheme. That is, if the previously saved credential |
| + is for https://example.com, a new credential for http://example.com would be |
| + blocked. More details can be found in the doc associated with |
| + http://crbug.com/571580. |
| + </summary> |
| +</histogram> |
| + |
| <histogram name="PasswordManager.ShouldShowAutoSignInFirstRunExperience" |
| enum="BooleanPending"> |
| <owner>vasilii@chromium.org</owner> |
