New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 658357 link

Starred by 5 users
Status: Duplicate
Merged: issue 658379
Owner:
█ spqc...@chromium.org
Last visit > 30 days ago
Closed: Oct 2016
Cc:
emilyschechter@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug
Team-Security-UX



Sign in to add a comment

HTTP-bad requires two flags

Project Member Reported by est...@chromium.org, Oct 21 2016 
Right now you have to flip both the "Security Chips" flag and the "Mark non-secure as" flag to see the "Not secure" omnibox warning.

This also means that users who have HTTP-bad enabled via the Finch trial will see no effect unless they've also flipped the "Security Chips" flag.

To fix this, we should control the Security Chips via a Finch trial, which is on 100% for canary and dev.

Comment 1 by est...@chromium.org, Oct 21 2016

Labels: -Pri-3 M-56 Pri-2
Owner: spqc...@chromium.org
Status: Assigned (was: Untriaged)
spqchan is working on this (we just wanted a public bug for tracking purposes)

Comment 2 by emilyschechter@chromium.org, Oct 21 2016 

 Issue 654227  has been merged into this issue.

Comment 3 by lgar...@chromium.org, Oct 26 2016

Components: UI>Browser>Omnibox>SecurityIndicators

Comment 4 by spqc...@chromium.org, Oct 26 2016 

Is this a duplicate of  Issue 658379 ?

Comment 5 by est...@chromium.org, Oct 26 2016

Mergedinto: 658379
Status: Duplicate (was: Assigned)
More or less, yeah.

Comment 6 by lgar...@chromium.org, Nov 24 2016

Components: -Security>UX
Labels: -Hotlist-SecurityIndicators
►

Sign in to add a comment