New issue
Advanced search Search tips

Issue 657500 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Payment Not Secure warning for Credit Card Input is lost after fwd/back navigation

Project Member Reported by elawrence@chromium.org, Oct 19 2016

Issue description

Version: 56.0.2895.0

What steps will reproduce the problem?
(1) Navigate to http://webdbg.com/test/forms/creditcard.asp
(2) Type in the Credit card field. Observe "Not Secure" field appears.
(3) Navigate to example.com using the omnibox.
(4) Click Back

Observe: Credit card data remains in field, but Not Secure label has vanished.
 

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

Labels: Hotlist-HttpBad
Components: UI>Browser>Omnibox>SecurityIndicators
Components: -Security>UX
Labels: -Hotlist-SecurityIndicators
Components: -UI>Browser>Omnibox>SecurityIndicators UI>Browser>Omnibox>SecurityIndicators>VerboseChip Internals>PageSecurityState
Components: -Internals>PageSecurityState -UI>Browser>Omnibox>SecurityIndicators>VerboseChip UI>Browser>Autofill
Labels: Hotlist-HttpBadFormNotSecure
Summary: Payment Not Secure warning for Credit Card Input is lost after fwd/back navigation (was: Not Secure warning for Credit Card INPUT is lost after fwd/back navigation)
This is actually not about the "Verbose Chip", but instead the on-field warning.

Arguably, this should be "Working as Intended" insofar as we don't otherwise show the on-field warnings when a page first loads, only when you actively engage with the input field.
Project Member

Comment 6 by sheriffbot@chromium.org, Apr 11 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
I don't think we need to fix this. We do show the "Not Secure" warning properly in the omnibox.

Sign in to add a comment