If you flip just security.insecure_connection_text.enabled and not
security.insecure_connection_icon.enabled you get Chrome's behavior.
Flipping both gives you the broken lock and the "Not Secure" text. I
don't see a big difference there and I hope we can ship this as soon
On Fri, Feb 9, 2018 at 1:55 AM, Martin Thomson <m...@mozilla.com> wrote:
> There's a tangible difference between text saying "Not Secure" and a
> broken lock icon. I think that we're close, but we'd be making a
> stronger statement than Chrome if we did this.
> On Fri, Feb 9, 2018 at 8:17 AM, Chris Peterson <cpeter...@mozilla.com> wrote:
>> Chrome will start marking HTTP pages as "Not secure" in July 2018 (Chrome
>> Firefox has a similar insecure HTTP warning icon, currently disabled by the
>> `security.insecure_connection_icon.enabled` pref added in bug 1310447.
>> Are there any blockers for Firefox shipping this feature?
>> dev-platform mailing list
> firefox-dev mailing list
dev-platform mailing list