Index: chrome/app/generated_resources.grd |
diff --git a/chrome/app/generated_resources.grd b/chrome/app/generated_resources.grd |
index b8386e8b334e7fae0b584588b23ea819dff02b0b..8f350dcec72b2545409c3a86debfe4c6ba52580f 100644 |
--- a/chrome/app/generated_resources.grd |
+++ b/chrome/app/generated_resources.grd |
@@ -9626,6 +9626,20 @@ and incorrect credentials. Either an attacker is trying to pretend to be <ph nam |
You cannot visit <ph name="SITE">$1<ex>google.com</ex></ph> right now because the website sent scrambled credentials that Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later. |
</message> |
+ <!-- Captive portal interstitial --> |
+ <message name="IDS_CAPTIVE_PORTAL_TITLE" desc="Title in the error page when a secure request is blocked because the network is redirecting the request to another page until the user logs in"> |
+ Connect to Network |
mmenke
2014/11/07 15:45:30
Has this gone through UI review? This feature sho
meacer
2014/11/07 20:30:31
Yes, in fact it went through a couple of UI iterat
|
+ </message> |
+ <message name="IDS_CAPTIVE_PORTAL_HEADING" desc="Heading in the error page when a secure request is blocked because a captive portal is manipulating a connection"> |
+ Connect to network |
+ </message> |
+ <message name="IDS_CAPTIVE_PORTAL_PRIMARY_PARAGRAPH" desc="The primary explanatory paragraph for the captive portal error page for network connections."> |
+ The network you are using may require you to visit its login page. |
+ </message> |
+ <message name="IDS_CAPTIVE_PORTAL_BUTTON_OPEN_LOGIN_PAGE" desc="Text for the open login page button"> |
+ Connect |
mmenke
2014/11/07 15:45:30
Login?
meacer
2014/11/07 20:30:31
While I agree with you, UI team prefers "connect"
|
+ </message> |
+ |
<!-- Misc strings for SSL UI --> |
<message name="IDS_UNSAFE_FRAME_MESSAGE" desc="The text displayed in the content that is subsituted to an unsafe frame."> |
This frame was blocked because it contains some insecure content. |