Show an infobar when VR services need to be installed or updated.

chrome/android/java/strings/android_chrome_strings.grd

Index: chrome/android/java/strings/android_chrome_strings.grd
diff --git a/chrome/android/java/strings/android_chrome_strings.grd b/chrome/android/java/strings/android_chrome_strings.grd
index 1dd39073127dff1104478551e8084d4945080c02..bebd331d22fe5fd931f64a4d25c442fa81586bde 100644
--- a/chrome/android/java/strings/android_chrome_strings.grd
+++ b/chrome/android/java/strings/android_chrome_strings.grd
@@ -2738,6 +2738,17 @@ You can control the Physical Web in Chrome Settings.
       <message name="IDS_KEYBOARD_SHORTCUT_WEBPAGE_GROUP_HEADER" desc="A text label that appears above a list of shortcuts that are related to manipulation of the current tab window. This group is part of several groups of keyboard shortcuts all shown in a dialog.">
         Webpage shortcuts
       </message>
+
+      <!-- VR services check infobar -->
+      <message name="IDS_VR_SERVICES_CHECK_INFOBAR_TEXT" desc="Text to displayed in the VR Services check infobar.">
+        To view virtual reality content, <ph name="ACTION">%s<ex>install</ex></ph> Google VR Services
+      </message>
+      <message name="IDS_VR_SERVICES_CHECK_INFOBAR_INSTALL_ACTION" desc="Text to be displayed in the VR Services check infobar text and confirm button for the install action">
+        install

[Bernhard Bauer, 2017/02/16 12:12:51]

According to
https://material.io/guidelines/components/buttons.html#buttons-style, text on
buttons should be capitalized (even if the button happens to render the text in
all-caps).

[amp, 2017/02/16 18:41:35]

I wondered if there might be some rule like that.  Thanks for the clarification.

So I'll go ahead and make 4 entries, 2 for the lower case used in the infobar
text, and 2 for the buttons which will be the same thing, just upper case.  Is
that the right way to do something like this?

[amp, 2017/02/17 01:50:39]

Done.

[Bernhard Bauer, 2017/02/17 16:14:16]

No, you don't need the full capitalization for the button, as the UI will do
that. What I would do however is split the IDS_VR_SERVICES_CHECK_INFOBAR_TEXT
pattern up into two full strings -- it's only marginally bigger (which might be
compressed away anyway) and reduces the chance for translation mistakes.

+      </message>
+      <message name="IDS_VR_SERVICES_CHECK_INFOBAR_UPDATE_ACTION" desc="Text to be displayed in the VR Services check infobar text and confirm button for the update action">
+        update
+      </message>
     </messages>
   </release>
 </grit>