[uber page] Migrate the virtual keyboard sub-page to a dialog

chrome/browser/resources/options2/chromeos/virtual_keyboard.html

Index: chrome/browser/resources/options2/chromeos/virtual_keyboard.html
diff --git a/chrome/browser/resources/options2/chromeos/virtual_keyboard.html b/chrome/browser/resources/options2/chromeos/virtual_keyboard.html
index 93a4f46dfa81a6b9d364d1ff8a56d4782b0df8c4..33e52eed2363e6b21503a0e345b1a43e4429d440 100644
--- a/chrome/browser/resources/options2/chromeos/virtual_keyboard.html
+++ b/chrome/browser/resources/options2/chromeos/virtual_keyboard.html
@@ -1,13 +1,20 @@
 <div id="virtual-keyboard-manager" class="page" hidden>

[Evan Stade, 2012/02/14 19:20:39]

should the file be called virtual_keyboard_overlay.html?

-  <header><h1 i18n-content="virtualKeyboardPage"></h1></header>
-  <div class="virtual-keyboard-column-headers">
-    <div class="virtual-keyboard-layout-column">
-      <h3 i18n-content="virtualKeyboardLayoutColumnTitle"></h3>
+  <h1 i18n-content="virtualKeyboardPage"></h1>
+  <div class="content-area">
+    <div class="virtual-keyboard-column-headers">
+      <div class="virtual-keyboard-layout-column">
+        <h3 i18n-content="virtualKeyboardLayoutColumnTitle"></h3>
+      </div>
+      <div class="virtual-keyboard-keyboard-column">
+        <h3 i18n-content="virtualKeyboardKeyboardColumnTitle"></h3>
+      </div>
     </div>
-    <div class="virtual-keyboard-keyboard-column">
-      <h3 i18n-content="virtualKeyboardKeyboardColumnTitle"></h3>
+    <list id="virtual-keyboard-per-layout-list"></list>
+    <!-- TODO(yusukes): Add virtual-keyboards-per-site elements. -->
+  </div>
+  <div class="action-area">
+    <div class="button-strip">
+      <button id="virtual-keyboard-overlay-confirm" i18n-content="ok"></button>
     </div>
   </div>
-  <list id="virtual-keyboard-per-layout-list"></list>
-  <!-- TODO(yusukes): Add virtual-keyboards-per-site elements. -->
 </div>