So, we could updating page title, page heading, security panel summary:

Page title: "Security error"
Page heading: "This page is not secure (broken HTTPS)."
Verbose security indicator: "Not secure"
Page info security summary: "Your connection to this site is not secure"
Security panel summary: "This page is not secure (broken HTTPS)."


@Adrienne -- I remember that "not secure" performed better than "not private" in the recent research. Did we think about updating the HTTPS warnings with the new string?

> So, we could updating page title, page heading, security panel summary:
> ...

Yep, those LGTM.

Re #1: We found that "not private" performed better on the interstitials themselves in an earlier round of surveys. People were more likely to think the warning was about Safe Browsing when we showed the "not secure" string.

It sounds like that might matter for page title ("privacy error" vs "security error").

So Lucas, maybe we should do

Page title: "Privacy error"
Page heading: "This page is not secure (broken HTTPS)."
Verbose security indicator: "Not secure"
Page info security summary: "Your connection to this site is not secure"
Security panel summary: "This page is not secure (broken HTTPS)."

I think Lucas put the wrong string in for page heading.

It's currently "Your connection is not private" and I'd like to keep it that way for now.

Yeah, that makes sense. I was just trying to change "insecure" to "not secure". Sounds like this is actually just in the security panel.

Yeah, "Page heading" in my first comment should have been "Your connection is not private". I pasted the wrong value due to  Issue 635656  (Regression: Can't copy from OSX interstitial page (again)). *sigh*

I'm sort of okay with using private for interstitials and "secure" for other stuff but I think it muddles our message:

- The verbose state "Not secure" shows up under a page title of "Privacy error" (shown in the tab strip).
- The page that calls itself a "privacy error" is called a "security warning" in Page Info

I can make a quick CL for DevTools, though.

Deleted: Screen Shot 2016-10-14 at 13.46.19.png 201 KB

	Screen Shot 2016-10-14 at 13.46.19.png 201 KB View Download

Deleted: Screen Shot 2016-10-14 at 13.47.47.png 82.6 KB

	Screen Shot 2016-10-14 at 13.47.47.png 82.6 KB View Download

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

commit 0e9e7f5f7700981206ca29133190091d62d58f26
Author: lgarron <lgarron@chromium.org>
Date: Tue Oct 18 02:24:57 2016

Change "insecure" to "not secure"/"non-secure" in DevTools.

BUG= 655886 

Review-Url: https://codereview.chromium.org/2420883003
Cr-Commit-Position: refs/heads/master@{#425861}

[modify] https://crrev.com/0e9e7f5f7700981206ca29133190091d62d58f26/third_party/WebKit/LayoutTests/http/tests/inspector/security/blocked-mixed-content-and-subresources-with-cert-errors-expected.txt
[modify] https://crrev.com/0e9e7f5f7700981206ca29133190091d62d58f26/third_party/WebKit/LayoutTests/http/tests/inspector/security/mixed-content-and-subresources-with-cert-errors-expected.txt
[modify] https://crrev.com/0e9e7f5f7700981206ca29133190091d62d58f26/third_party/WebKit/LayoutTests/http/tests/inspector/security/security-blocked-mixed-content-expected.txt
[modify] https://crrev.com/0e9e7f5f7700981206ca29133190091d62d58f26/third_party/WebKit/Source/devtools/front_end/security/SecurityPanel.js