Fix privacy whitepaper link

chrome/browser/ssl/captive_portal_blocking_page.cc

Index: chrome/browser/ssl/captive_portal_blocking_page.cc
diff --git a/chrome/browser/ssl/captive_portal_blocking_page.cc b/chrome/browser/ssl/captive_portal_blocking_page.cc
index d0c3cd2036fadc68463c34c0a806523680e1fc72..206fd81fbe95279b6cbb0263b14c9996e0eca2b2 100644
--- a/chrome/browser/ssl/captive_portal_blocking_page.cc
+++ b/chrome/browser/ssl/captive_portal_blocking_page.cc
@@ -233,6 +233,9 @@ void CaptivePortalBlockingPage::CommandReceived(const std::string& command) {
     case security_interstitials::CMD_OPEN_REPORTING_PRIVACY:
       controller()->OpenExtendedReportingPrivacyPolicy();
       break;
+    case security_interstitials::CMD_OPEN_WHITEPAPER:
+      controller()->OpenExtendedReportingWhitepaper();
+      break;

[meacer, 2016/11/22 19:57:23]

Captive portal interstitial only has a single "Connect" button without any links
(chrome://interstitials/captiveportal), so I'm not sure if this code can
actually be reached? Should we actually put a "learn more" link?

[Jialiu Lin, 2016/11/22 21:06:13]

Thanks for catching this! I didn't read the code careful enough. I though every
SecurityInterstitial subclass would have a SBER opt-in checkbox (And apparently
it is not the case :-P).
I reverted the change made on captive_portal_clocking_page.cc
CL description fixed too.

[meacer, 2016/11/22 21:25:22]

Apologies, I'm mistaken. We do in fact show the SBER opt-in checkbox, but the
chrome://interstitials page doesn't do that.

I'm guessing "Automatically report" link opens the privacy whitepaper? If so,
this LGTM.

     case security_interstitials::CMD_ERROR:
     case security_interstitials::CMD_TEXT_FOUND:
     case security_interstitials::CMD_TEXT_NOT_FOUND: