Add flags for new Autofill work.

chrome/app/generated_resources.grd

 <?xml version="1.0" encoding="utf-8"?>
 
 <!--
 This file contains definitions of resources that will be translated for each
 locale.  The variables is_win, is_macosx, is_linux, and is_posix are available
 for making strings OS specific.  Other platform defines such as use_titlecase
 are declared in build/common.gypi.
 -->
 
 <grit base_dir="." latest_public_release="0" current_release="1"
@@ skipping 5967 matching lines @@
       <message name="IDS_FLAGS_ENABLE_AUTOLOGIN_DESCRIPTION" desc="Description for the flag to pre-login the user">
         When enabled, visiting a Google account login page will trigger an infobar allowing easy sign in with the Google account connected to the profile.
         Auto-login is always disabled if the profile is not connected to an account, regardless of this flag.
       </message>
       <message name="IDS_FLAGS_SHOW_AUTOFILL_TYPE_PREDICTIONS_NAME" desc="Title for the flag to show Autofill field type predictions for all forms">
         Show Autofill predictions
       </message>
       <message name="IDS_FLAGS_SHOW_AUTOFILL_TYPE_PREDICTIONS_DESCRIPTION" desc="Description for the flag to show Autofill field type predictions for all forms">
         Annotates web forms with Autofill field type predictions as placeholder text.
       </message>
+      <message name="IDS_FLAGS_ENABLE_NEW_AUTOFILL_UI_NAME" desc="Title for the flag to enable the new Autofill UI">
+        Enable new Autofill UI
+      </message>
+      <message name="IDS_FLAGS_ENABLE_NEW_AUTOFILL_UI_DESCRIPTION" desc="Description for the flag to enable the new Autofill UI">
+        Enable the new Autofill UI (feature in progress).

[Nico, 2012/10/23 21:47:33]

Everything on flags is in progress, no need to call that out. Also, this just
repeats the title, maybe something more describing what this is ("The new UI
shows a blargle instead of the old behavior of foobling")

[Ilya Sherman, 2012/10/23 21:58:08]

Done, though the new descriptions are perhaps a little too verbose; and at the
same time a little imprecise, because making them precise would require even
more verbosity.

+      </message>
+      <message name="IDS_FLAGS_ENABLE_NEW_AUTOFILL_HEURISTICS_NAME" desc="Title for the flag to enable new Autofill heuristics">
+        Enable new Autofill heuristics
+      </message>
+      <message name="IDS_FLAGS_ENABLE_NEW_AUTOFILL_HEURISTICS_DESCRIPTION" desc="Description for the flag to enable new Autofill heuristics">
+        Enable new Autofill heuristics (feature in progress).
+      </message>
       <message name="IDS_FLAGS_SYNC_SEARCH_ENGINES_NAME" desc="Title for the flag to enable syncing the Search Engines datatype">
         Enable syncing search engines
       </message>
       <message name="IDS_FLAGS_SYNC_SEARCH_ENGINES_DESCRIPTION" desc="Description for the flag to enable syncing the Search Engines datatype">
         Enable search engines in the sync settings. This allows syncing your custom search engines to other clients.
       </message>
       <message name="IDS_FLAGS_SYNC_TABS_NAME" desc="Title for the flag to enable syncing the open tabs datatype">
         Enable syncing open tabs
       </message>
       <message name="IDS_FLAGS_SYNC_TABS_DESCRIPTION" desc="Description for the flag to enable syncing the open tabs datatype">
@@ skipping 8674 matching lines @@
 
     <structures fallback_to_english="true">
       <!-- Make sure these stay in sync with the structures in generated_resources.grd. -->
       <structure name="IDD_CHROME_FRAME_FIND_DIALOG" file="cf_resources.rc" type="dialog" >
       </structure>
       <structure name="IDD_CHROME_FRAME_READY_PROMPT" file="cf_resources.rc" type="dialog" >
       </structure>
     </structures>
   </release>
 </grit>