Index: chrome/app/generated_resources.grd |
diff --git a/chrome/app/generated_resources.grd b/chrome/app/generated_resources.grd |
index 4cad13ae845b09db4a9796b0736d1c6a7bcee1d1..ac1a76f4f61190a32d675763a4894bc8b8125b20 100644 |
--- a/chrome/app/generated_resources.grd |
+++ b/chrome/app/generated_resources.grd |
@@ -5620,7 +5620,13 @@ Keep your key file in a safe place. You will need it to create new versions of y |
Gesture requirement for media playback |
</message> |
<message name="IDS_FLAGS_GESTURE_REQUIREMENT_FOR_MEDIA_PLAYBACK_DESCRIPTION" desc="Description for the flag for gesture requiment for media playback"> |
- User gesture requirement for playing media elements. Disabling this will allow autoplay to work. |
+ User gesture requirement for playing media elements. Disabling this will allow auto-starting presentations. |
whywhat
2016/02/04 20:39:08
I don't think we need chrome://flags for automated
Zhiqiang Zhang (Slow)
2016/02/05 16:20:33
Done.
|
+ </message> |
+ <message name="IDS_FLAGS_GESTURE_REQUIREMENT_FOR_PRESENTATION_NAME" desc="Title for the flag for gesture requiment for presentation"> |
+ Gesture requirement for presentation |
+ </message> |
+ <message name="IDS_FLAGS_GESTURE_REQUIREMENT_FOR_PRESENTATION_DESCRIPTION" desc="Description for the flag for gesture requiment for presentation"> |
+ User gesture requirement for presentation. Disabling this will allow auto-starting presentations. |
</message> |
<if expr="use_ash"> |
<message name="IDS_FLAGS_ASH_MAXIMIZE_MODE_WINDOW_BACKDROP_NAME" desc="Title for the flag which can be used for window backdrops in TouchView."> |
@@ -5981,7 +5987,7 @@ Keep your key file in a safe place. You will need it to create new versions of y |
Enable the "stale-while-revalidate" cache directive |
</message> |
<message name="IDS_FLAGS_ENABLE_STALE_WHILE_REVALIDATE_DESCRIPTION" desc="Description of the flag to enable the "stale-while-revalidate" cache directive. This message is intended for web developers who are familiar with technical terms. "Cache-Control: stale-while-revalidate" is the literal string sent by the HTTP server, and so should be untranslated where possible. If necessary for translation it can be split into the HTTP header name part "Cache-Control" and the value part "stale-while-revalidate". "directive" here is an instruction sent by an HTTP server to indicate what caching behaviour should be used. The directive is typically configured by the server administrator. "servers" here refers to HTTP server software. "resources" here means individual files served by HTTP servers and cached by the browser. "be revalidated" means "be checked with the HTTP server whether or not the browser has the latest version". "in the background" here means without making the user wait. "latency" here refers to the time the user waits for a web page to be loaded or become usable."> |
- Enable the experimental implementation of the "Cache-Control: stale-while-revalidate" directive. This permits servers to specify that some resources may be revalidated in the background to improve latency. |
+ Enable the experimental implementation of the "Cache-Control: stale-while-revalidate" directive. This permits servers to specify that some resources may be revalidated in the background to improve latency. |
</message> |
</if> |
<message name="IDS_FLAGS_ENABLE_NAVIGATION_TRACING" desc="Name of the flag to enable navigation tracing"> |
@@ -14341,7 +14347,7 @@ Please check your email at <ph name="ACCOUNT_EMAIL">$2<ex>jane.doe@gmail.com</ex |
<message name="IDS_CREDENTIAL_MANAGEMENT_ACCOUNT_CHOOSER_NO_THANKS" desc="Text of the button to dismiss the account chooser."> |
No thanks |
</message> |
- |
+ |
<message name="IDS_ALLOW_INSECURE_LOCALHOST" desc="Name of the 'Allow insecure localhost' flag."> |
Allow invalid certificates for resources loaded from localhost. |
</message> |