New issue
Advanced search Search tips

Issue 839969 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 1
Type: Bug
Team-Security-UX



Sign in to add a comment

Add a message to the SSL interstitial when users see frequent warnings

Project Member Reported by est...@chromium.org, May 4 2018

Issue description

Some error codes (net::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED, net::ERR_CERT_SYMANTEC_LEGACY) may result in frequent interstitials for a time. If a user sees more than some number of these during a browsing session, we'd like to add a message to the interstitial telling them to check back in a few days.
 
Project Member

Comment 2 by bugdroid1@chromium.org, May 9 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9e58df467024fa836bcea8c3e49805f1be2ab66b

commit 9e58df467024fa836bcea8c3e49805f1be2ab66b
Author: Emily Stark <estark@google.com>
Date: Wed May 09 15:25:14 2018

Show the recurrent error message on the interstitial

When an error message has recurred several times, show a message on the
interstitial. Note: the message isn't styled yet; the feature is off by default
so I'll do the styling (and translation screenshot) in a follow-up CL.

Bug:  839969 
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I94a31ff16eaf9e8ef82134f372852f03b19e28df
Reviewed-on: https://chromium-review.googlesource.com/1049119
Commit-Queue: Emily Stark <estark@chromium.org>
Reviewed-by: Christopher Thompson <cthomp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#557190}
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/chrome/browser/ssl/bad_clock_blocking_page.cc
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/chrome/browser/ssl/captive_portal_blocking_page.cc
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/chrome/browser/ssl/captive_portal_blocking_page.h
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/chrome/browser/ssl/captive_portal_blocking_page_browsertest.cc
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/chrome/browser/ssl/mitm_software_blocking_page.cc
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/chrome/browser/ssl/ssl_blocking_page.cc
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/chrome/browser/ssl/ssl_browsertest.cc
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/chrome/browser/ssl/ssl_error_controller_client.cc
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/chrome/browser/ssl/ssl_error_controller_client.h
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/chrome/browser/ssl/ssl_error_handler.cc
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/chrome/browser/ui/webui/interstitials/interstitial_ui.cc
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/components/security_interstitials/core/browser/resources/interstitial_large.html
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/components/security_interstitials/core/browser/resources/interstitial_large.js
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/components/security_interstitials/core/common_string_util.cc
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/components/security_interstitials/core/controller_client.cc
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/components/security_interstitials/core/controller_client.h
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/components/security_interstitials/core/safe_browsing_loud_error_ui.cc
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/components/security_interstitials/core/safe_browsing_quiet_error_ui.cc
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/components/security_interstitials/core/ssl_error_ui.cc
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/components/security_interstitials/core/superfish_error_ui.cc
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/components/security_interstitials_strings.grdp
[modify] https://crrev.com/9e58df467024fa836bcea8c3e49805f1be2ab66b/ios/chrome/browser/ssl/ios_captive_portal_blocking_page.mm

Haven't gotten redlines from Max yet but here's a screenshot of the rough styling.
Screen Shot 2018-05-09 at 12.38.28 PM.png
110 KB View Download
Project Member

Comment 4 by bugdroid1@chromium.org, May 10 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/541ee9fe1a988b1c2428462acbe21daade632d7f

commit 541ee9fe1a988b1c2428462acbe21daade632d7f
Author: Emily Stark <estark@google.com>
Date: Thu May 10 14:39:11 2018

Add CSS for recurrent error message

When an error message has recurred several times, show a message on the
interstitial. This CL adds the CSS for the recurrent error message. See
https://bugs.chromium.org/p/chromium/issues/detail?id=839969#c3 for a current
screenshot.

Bug:  839969 
Change-Id: I4a3ce380563d7053bf6d241ae18a380f67d22300
Reviewed-on: https://chromium-review.googlesource.com/1052918
Commit-Queue: Emily Stark <estark@chromium.org>
Reviewed-by: Edward Jung <edwardjung@chromium.org>
Cr-Commit-Position: refs/heads/master@{#557513}
[modify] https://crrev.com/541ee9fe1a988b1c2428462acbe21daade632d7f/components/security_interstitials/core/browser/resources/interstitial_large.js
[modify] https://crrev.com/541ee9fe1a988b1c2428462acbe21daade632d7f/components/security_interstitials/core/common/resources/interstitial_common.css

Project Member

Comment 5 by bugdroid1@chromium.org, May 11 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/c657d45e536fd43357f9d90b529ce52d42138c1c

commit c657d45e536fd43357f9d90b529ce52d42138c1c
Author: Emily Stark <estark@google.com>
Date: Fri May 11 19:03:19 2018

Implement a pref mode for the recurrent error message

When a certificate error recurs multiple times within a browsing session, we add
a special message to the interstitial. This CL adds a Finch-controlled mode
where the count of certificate errors is stored in a pref instead of in memory,
so that we can trigger the recurrent error message when an error recurs within a
certain period of time (even spanning browsing sessions). We might want to roll
out this pref mode on certain platforms (like Android) where browsing sessions
might be significantly shorter than desktop.

Bug:  839969 
Change-Id: I04f1af1aa30043821859f4459602627b9ba7af77
Reviewed-on: https://chromium-review.googlesource.com/1053563
Commit-Queue: Emily Stark <estark@chromium.org>
Reviewed-by: Christopher Thompson <cthomp@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#557966}
[modify] https://crrev.com/c657d45e536fd43357f9d90b529ce52d42138c1c/chrome/browser/prefs/browser_prefs.cc
[modify] https://crrev.com/c657d45e536fd43357f9d90b529ce52d42138c1c/chrome/browser/profiles/profile.cc
[modify] https://crrev.com/c657d45e536fd43357f9d90b529ce52d42138c1c/chrome/browser/ssl/chrome_ssl_host_state_delegate.cc
[modify] https://crrev.com/c657d45e536fd43357f9d90b529ce52d42138c1c/chrome/browser/ssl/chrome_ssl_host_state_delegate.h
[modify] https://crrev.com/c657d45e536fd43357f9d90b529ce52d42138c1c/chrome/browser/ssl/chrome_ssl_host_state_delegate_test.cc
[modify] https://crrev.com/c657d45e536fd43357f9d90b529ce52d42138c1c/chrome/common/pref_names.cc
[modify] https://crrev.com/c657d45e536fd43357f9d90b529ce52d42138c1c/chrome/common/pref_names.h

Project Member

Comment 6 by bugdroid1@chromium.org, May 11 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/c657d45e536fd43357f9d90b529ce52d42138c1c

commit c657d45e536fd43357f9d90b529ce52d42138c1c
Author: Emily Stark <estark@google.com>
Date: Fri May 11 19:03:19 2018

Implement a pref mode for the recurrent error message

When a certificate error recurs multiple times within a browsing session, we add
a special message to the interstitial. This CL adds a Finch-controlled mode
where the count of certificate errors is stored in a pref instead of in memory,
so that we can trigger the recurrent error message when an error recurs within a
certain period of time (even spanning browsing sessions). We might want to roll
out this pref mode on certain platforms (like Android) where browsing sessions
might be significantly shorter than desktop.

Bug:  839969 
Change-Id: I04f1af1aa30043821859f4459602627b9ba7af77
Reviewed-on: https://chromium-review.googlesource.com/1053563
Commit-Queue: Emily Stark <estark@chromium.org>
Reviewed-by: Christopher Thompson <cthomp@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#557966}
[modify] https://crrev.com/c657d45e536fd43357f9d90b529ce52d42138c1c/chrome/browser/prefs/browser_prefs.cc
[modify] https://crrev.com/c657d45e536fd43357f9d90b529ce52d42138c1c/chrome/browser/profiles/profile.cc
[modify] https://crrev.com/c657d45e536fd43357f9d90b529ce52d42138c1c/chrome/browser/ssl/chrome_ssl_host_state_delegate.cc
[modify] https://crrev.com/c657d45e536fd43357f9d90b529ce52d42138c1c/chrome/browser/ssl/chrome_ssl_host_state_delegate.h
[modify] https://crrev.com/c657d45e536fd43357f9d90b529ce52d42138c1c/chrome/browser/ssl/chrome_ssl_host_state_delegate_test.cc
[modify] https://crrev.com/c657d45e536fd43357f9d90b529ce52d42138c1c/chrome/common/pref_names.cc
[modify] https://crrev.com/c657d45e536fd43357f9d90b529ce52d42138c1c/chrome/common/pref_names.h

Project Member

Comment 8 by bugdroid1@chromium.org, May 15 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b873b84414c1b8f42134f9b0e72f16b72a4c1711

commit b873b84414c1b8f42134f9b0e72f16b72a4c1711
Author: Emily Stark <estark@google.com>
Date: Tue May 15 14:26:02 2018

Update recurrent interstitial CSS to match specs

Bug:  839969 
Change-Id: I5c0de5f31d997be815a2c956e279f06dc1047d84
Reviewed-on: https://chromium-review.googlesource.com/1058113
Reviewed-by: Edward Jung <edwardjung@chromium.org>
Commit-Queue: Emily Stark <estark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#558698}
[modify] https://crrev.com/b873b84414c1b8f42134f9b0e72f16b72a4c1711/components/security_interstitials/core/browser/resources/interstitial_large.html
[modify] https://crrev.com/b873b84414c1b8f42134f9b0e72f16b72a4c1711/components/security_interstitials/core/common/resources/interstitial_common.css

Comment 9 by est...@chromium.org, May 15 2018

Status: Fixed (was: Assigned)
Project Member

Comment 10 by bugdroid1@chromium.org, May 25 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6f5dc831f7c28f25b41c4bf0ae19e07f78663819

commit 6f5dc831f7c28f25b41c4bf0ae19e07f78663819
Author: Emily Stark <estark@google.com>
Date: Fri May 25 03:25:00 2018

Add some metrics for the recurrent interstitial feature

This CL adds two metrics of interest for the recurrent interstitial UI that is
shown when the user sees the same error code multiples times. The metrics record
how often the recurrent interstitial is shown (split by
overridable/nonoverridable) and when the user proceeds through a recurrent
interstitial, so that we can check whether the clickthrough rate is higher for
recurrent interstitials than normal SSL interstitials.

I've also added an additional parameter to the field trial to control whether the
recurrent error message is actually displayed on the interstitial. This allows us
to configure an experiment group in which recurrent errors are tracked and
histograms are recorded but the recurrent error message isn't actually shown, so
that we can compare clickthrough rates for identical error conditions with and
without the recurrent error message showing up.

Bug:  839969 
Change-Id: I3739b193b9d35e9d75dc584a77514a22a5f1356b
Reviewed-on: https://chromium-review.googlesource.com/1071069
Commit-Queue: Emily Stark <estark@chromium.org>
Reviewed-by: Christopher Thompson <cthomp@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#561755}
[modify] https://crrev.com/6f5dc831f7c28f25b41c4bf0ae19e07f78663819/chrome/browser/ssl/chrome_ssl_host_state_delegate.cc
[modify] https://crrev.com/6f5dc831f7c28f25b41c4bf0ae19e07f78663819/chrome/browser/ssl/chrome_ssl_host_state_delegate.h
[modify] https://crrev.com/6f5dc831f7c28f25b41c4bf0ae19e07f78663819/chrome/browser/ssl/ssl_blocking_page.cc
[modify] https://crrev.com/6f5dc831f7c28f25b41c4bf0ae19e07f78663819/chrome/browser/ssl/ssl_browsertest.cc
[modify] https://crrev.com/6f5dc831f7c28f25b41c4bf0ae19e07f78663819/chrome/browser/ssl/ssl_error_controller_client.cc
[modify] https://crrev.com/6f5dc831f7c28f25b41c4bf0ae19e07f78663819/chrome/browser/ssl/ssl_error_controller_client.h
[modify] https://crrev.com/6f5dc831f7c28f25b41c4bf0ae19e07f78663819/tools/metrics/histograms/enums.xml
[modify] https://crrev.com/6f5dc831f7c28f25b41c4bf0ae19e07f78663819/tools/metrics/histograms/histograms.xml

Project Member

Comment 11 by bugdroid1@chromium.org, May 26 2018

Labels: Merge-Request-68
Requesting a merge for the change in c10. This is a metrics change that is covered by automated tests and has been baking on canary; I've verified that the UMA metrics from canary look as expected.
Project Member

Comment 13 by sheriffbot@chromium.org, May 29 2018

Labels: -Merge-Request-68 Hotlist-Merge-Review Merge-Review-68
This bug requires manual review: There is .grd file changes and we are only 55 days from stable.
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), kariahda@(iOS), bhthompson@(ChromeOS), abdulsyed@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Note to TPMs re c13: the change that (c10) I need to merge doesn't have grd file changes.
Labels: -Merge-Review-68 Merge-Approved-68
Branch:3440
Project Member

Comment 16 by bugdroid1@chromium.org, May 29 2018

Labels: -merge-approved-68 merge-merged-3440
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ad75ea8bb6c781c25e8c10a4355c6e9ac486c832

commit ad75ea8bb6c781c25e8c10a4355c6e9ac486c832
Author: Emily Stark <estark@google.com>
Date: Tue May 29 20:22:25 2018

Add some metrics for the recurrent interstitial feature

This CL adds two metrics of interest for the recurrent interstitial UI that is
shown when the user sees the same error code multiples times. The metrics record
how often the recurrent interstitial is shown (split by
overridable/nonoverridable) and when the user proceeds through a recurrent
interstitial, so that we can check whether the clickthrough rate is higher for
recurrent interstitials than normal SSL interstitials.

I've also added an additional parameter to the field trial to control whether the
recurrent error message is actually displayed on the interstitial. This allows us
to configure an experiment group in which recurrent errors are tracked and
histograms are recorded but the recurrent error message isn't actually shown, so
that we can compare clickthrough rates for identical error conditions with and
without the recurrent error message showing up.

Bug:  839969 
Change-Id: I3739b193b9d35e9d75dc584a77514a22a5f1356b
Reviewed-on: https://chromium-review.googlesource.com/1071069
Commit-Queue: Emily Stark <estark@chromium.org>
Reviewed-by: Christopher Thompson <cthomp@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#561755}(cherry picked from commit 6f5dc831f7c28f25b41c4bf0ae19e07f78663819)
Reviewed-on: https://chromium-review.googlesource.com/1077032
Reviewed-by: Emily Stark <estark@chromium.org>
Cr-Commit-Position: refs/branch-heads/3440@{#34}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[modify] https://crrev.com/ad75ea8bb6c781c25e8c10a4355c6e9ac486c832/chrome/browser/ssl/chrome_ssl_host_state_delegate.cc
[modify] https://crrev.com/ad75ea8bb6c781c25e8c10a4355c6e9ac486c832/chrome/browser/ssl/chrome_ssl_host_state_delegate.h
[modify] https://crrev.com/ad75ea8bb6c781c25e8c10a4355c6e9ac486c832/chrome/browser/ssl/ssl_blocking_page.cc
[modify] https://crrev.com/ad75ea8bb6c781c25e8c10a4355c6e9ac486c832/chrome/browser/ssl/ssl_browsertest.cc
[modify] https://crrev.com/ad75ea8bb6c781c25e8c10a4355c6e9ac486c832/chrome/browser/ssl/ssl_error_controller_client.cc
[modify] https://crrev.com/ad75ea8bb6c781c25e8c10a4355c6e9ac486c832/chrome/browser/ssl/ssl_error_controller_client.h
[modify] https://crrev.com/ad75ea8bb6c781c25e8c10a4355c6e9ac486c832/tools/metrics/histograms/enums.xml
[modify] https://crrev.com/ad75ea8bb6c781c25e8c10a4355c6e9ac486c832/tools/metrics/histograms/histograms.xml

Project Member

Comment 17 by bugdroid1@chromium.org, May 30 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9e7b681eaa5d1c787a71daf4841be6ffa79549d3

commit 9e7b681eaa5d1c787a71daf4841be6ffa79549d3
Author: Emily Stark <estark@google.com>
Date: Wed May 30 17:56:24 2018

Default to showing recurrent interstitial UI with unset parameter

In https://chromium-review.googlesource.com/c/chromium/src/+/1071069, I added a
Finch parameter to control whether the recurrent interstitial UI actually shows
up or not (so that we could have a control group that doesn't show the UI for
comparison). I defaulted the UI to be hidden if the parameter is unset, but this
CL changes it to default to show if the parameter is unset. This isn't important
for the experiment or functionality; it's purely to facilitate testing on
Android and ChromeOS where the parameter is unset after toggling the flag in
chrome://flags.

Bug:  839969 
Change-Id: If51e7fdeaef2c57a81c0b1da0110d8f953b06539
Reviewed-on: https://chromium-review.googlesource.com/1079407
Reviewed-by: Christopher Thompson <cthomp@chromium.org>
Commit-Queue: Emily Stark <estark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#562905}
[modify] https://crrev.com/9e7b681eaa5d1c787a71daf4841be6ffa79549d3/chrome/browser/ssl/ssl_error_controller_client.cc

Labels: Merge-Request-68
Requesting an additional merge for #17. This is a one-line change that won't affect behavior for users in the field trial, it simply facilitates testing with chrome://flags.
Project Member

Comment 19 by sheriffbot@chromium.org, Jun 1 2018

Labels: -Merge-Request-68 Merge-Review-68
This bug requires manual review: There is .grd file changes and we are only 52 days from stable.
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), kariahda@(iOS), bhthompson@(ChromeOS), abdulsyed@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
(no .grd file changes because I only want to merge #17)
Labels: -Merge-Review-68 Merge-Approved-68
Approved - branch:3440
Project Member

Comment 22 by bugdroid1@chromium.org, Jun 4 2018

Labels: -merge-approved-68
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0cfc37a62be053af5bb769dd17e62f98576c757b

commit 0cfc37a62be053af5bb769dd17e62f98576c757b
Author: Emily Stark <estark@google.com>
Date: Mon Jun 04 20:38:17 2018

Default to showing recurrent interstitial UI with unset parameter

In https://chromium-review.googlesource.com/c/chromium/src/+/1071069, I added a
Finch parameter to control whether the recurrent interstitial UI actually shows
up or not (so that we could have a control group that doesn't show the UI for
comparison). I defaulted the UI to be hidden if the parameter is unset, but this
CL changes it to default to show if the parameter is unset. This isn't important
for the experiment or functionality; it's purely to facilitate testing on
Android and ChromeOS where the parameter is unset after toggling the flag in
chrome://flags.

Bug:  839969 
Change-Id: If51e7fdeaef2c57a81c0b1da0110d8f953b06539
Reviewed-on: https://chromium-review.googlesource.com/1079407
Reviewed-by: Christopher Thompson <cthomp@chromium.org>
Commit-Queue: Emily Stark <estark@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#562905}(cherry picked from commit 9e7b681eaa5d1c787a71daf4841be6ffa79549d3)
Reviewed-on: https://chromium-review.googlesource.com/1085973
Reviewed-by: Emily Stark <estark@chromium.org>
Cr-Commit-Position: refs/branch-heads/3440@{#168}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[modify] https://crrev.com/0cfc37a62be053af5bb769dd17e62f98576c757b/chrome/browser/ssl/ssl_error_controller_client.cc

Project Member

Comment 23 by bugdroid1@chromium.org, Jun 12 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/541e64f39d4879fc20946ddc3ada66d44ddc66af

commit 541e64f39d4879fc20946ddc3ada66d44ddc66af
Author: Emily Stark <estark@google.com>
Date: Tue Jun 12 21:39:09 2018

Turn on recurrent interstitial in field trial testing config

Bug:  839969 
Change-Id: Ib677bf13f737e5cc2fb5cd5b43466f2d6b796f69
Reviewed-on: https://chromium-review.googlesource.com/1096370
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Commit-Queue: Emily Stark <estark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#566580}
[modify] https://crrev.com/541e64f39d4879fc20946ddc3ada66d44ddc66af/testing/variations/fieldtrial_testing_config.json

Project Member

Comment 24 by bugdroid1@chromium.org, Jul 13

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/17667924bdcdf48ad56f3955f866f28fecbb0091

commit 17667924bdcdf48ad56f3955f866f28fecbb0091
Author: Emily Stark <estark@google.com>
Date: Fri Jul 13 20:27:11 2018

Add Android field trial config for recurrent interstitial

Bug:  839969 
Change-Id: I07ad560f50aa25a10a5a9fb55ebdd525d0fa6e84
Reviewed-on: https://chromium-review.googlesource.com/1136711
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Emily Stark <estark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575054}
[modify] https://crrev.com/17667924bdcdf48ad56f3955f866f28fecbb0091/testing/variations/fieldtrial_testing_config.json

Project Member

Comment 25 by bugdroid1@chromium.org, Jul 13

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/89e8120b30ff3138cde3a4791e979b14c22cd44e

commit 89e8120b30ff3138cde3a4791e979b14c22cd44e
Author: Emily Stark <estark@google.com>
Date: Fri Jul 13 20:30:58 2018

Split out recurrent error metrics for CT errors specifically

This will allow us to see whether the recurrent interstitial message affects CTR
for CT errors specifically (rather than lumping them in with Symantec distrust
errors, which can also trigger the recurrent error message).

Bug:  839969 
Change-Id: I04764573c6f225ab25c61fb268983f02f38fdc3f
Reviewed-on: https://chromium-review.googlesource.com/1136717
Reviewed-by: Christopher Thompson <cthomp@chromium.org>
Reviewed-by: Robert Kaplow (slow) <rkaplow@chromium.org>
Commit-Queue: Emily Stark <estark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575056}
[modify] https://crrev.com/89e8120b30ff3138cde3a4791e979b14c22cd44e/chrome/browser/ssl/ssl_blocking_page.cc
[modify] https://crrev.com/89e8120b30ff3138cde3a4791e979b14c22cd44e/chrome/browser/ssl/ssl_error_controller_client.cc
[modify] https://crrev.com/89e8120b30ff3138cde3a4791e979b14c22cd44e/tools/metrics/histograms/histograms.xml

Sign in to add a comment