chrome/app/generated_resources.grd

Index: chrome/app/generated_resources.grd
diff --git a/chrome/app/generated_resources.grd b/chrome/app/generated_resources.grd
index 081afb9e3fc1255e0cc079d72c52a772d0ec9e20..89a870170d80e3117e65dbf0c4b4388c4246e30e 100644
--- a/chrome/app/generated_resources.grd
+++ b/chrome/app/generated_resources.grd
@@ -8024,13 +8024,13 @@ Keep your key file in a safe place. You will need it to create new versions of y
         Plug-in exceptions
       </message>
       <message name="IDS_PLUGIN_LOAD_RADIO" desc="A radio button in the Content Settings dialog for allowing plug-ins use on any site.">
-        Run automatically (recommended)
+        Run all plugin content (recommended)
       </message>
-      <message name="IDS_PLUGIN_ASK_RADIO" desc="A radio button in the Content Settings dialog for gating plug-ins on a mouse click (left button).">
-        Click to play

[Bernhard Bauer, 2014/12/11 14:42:21]

Hm... this changes the semantics of click-to-play, which might not be what
existing users expect.

Also, have these strings been reviewed?

[tommycli, 2014/12/11 17:11:19]

Yes. The behavior is going to change.

[Bernhard Bauer, 2014/12/11 17:28:29]

OK... Given that this uses content settings behind the scenes and therefore can
have site-specific exceptions, have we thought about integrating with that?

+      <message name="IDS_PLUGIN_ASK_RADIO" desc="A radio button in the Content Settings dialog for detecting and running important plugin content only.">
+        Detect and run important plugin content
       </message>
       <message name="IDS_PLUGIN_ASK_MENU_RADIO" desc="A radio button in the Content Settings dialog for gating plug-ins on a context menu activation.">
-        Block by default (You can manually run a blocked plug-in at any time.)
+        Do not run plugins by default
       </message>
       <message name="IDS_PLUGIN_SELECTIVE_DISABLE" desc="Link to selectively disable plug-ins">
         Disable individual plug-ins...