Assigning to meacer to tell me if this is WAI or not.

I can see an argument for not showing a scary red triangle in this situation, but it's inconsistent with the bad clock interstitial which do show a red triangle.

If we want to fix this it's probably just a matter of implementing OverrideEntry in CaptivePortalBlockingPage.

Also note that you can't test this with chrome://interstitials, which always use (i) icons.

I'd be okay with this given that there is no way to proceed through this interstitial, but since bad clock also uses red triangle it makes sense to change it.

Yeah, that makes sense to me too -- I'll send you a CL.

Removing security labels since it's a non-overrideable interstitial, not really a security bug.

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

commit 3e2553a9defa7bdf50be5d18f0cb8ce4ec539ad9
Author: estark <estark@chromium.org>
Date: Mon Oct 10 22:25:34 2016

Show red lock icon on captive portal SSL interstitial

We were previously showing the neutral icon on captive portal
interstitials. This isn't that big a deal because the interstitial is
non-bypassable, but we should show a red/dangerous icon to be consistent
with the bad clock interstitial.

BUG= 653779 

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

[modify] https://crrev.com/3e2553a9defa7bdf50be5d18f0cb8ce4ec539ad9/chrome/browser/ssl/captive_portal_blocking_page.cc
[modify] https://crrev.com/3e2553a9defa7bdf50be5d18f0cb8ce4ec539ad9/chrome/browser/ssl/captive_portal_blocking_page.h
[modify] https://crrev.com/3e2553a9defa7bdf50be5d18f0cb8ce4ec539ad9/chrome/browser/ssl/captive_portal_blocking_page_browsertest.cc

Security>UX component is deprecated in favor of the Team-Security-UX label

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot