Add a new flag for HTTP-bad Phase 1 development work
This extends the #mark-non-secure-as flag to use for the HTTP-bad phase 1 (passwords and CC form detection) work. It currently behaves exactly like the existing kMarkNonSecureAsNeutral switch, although presumably that will change as we make progress. BUG=646221 Review-Url: https://codereview.chromium.org/2337103002 Cr-Commit-Position: refs/heads/master@{#418860}
Showing
Please register or sign in to comment