Polished UI for the host side of pairing flow.

chrome/browser/resources/chromeos/login/oobe.html

Index: chrome/browser/resources/chromeos/login/oobe.html
diff --git a/chrome/browser/resources/chromeos/login/oobe.html b/chrome/browser/resources/chromeos/login/oobe.html
index 44d0eaa3cc66d7f4460a5900fd5d3dd28607595e..1a2be44dfd93c622505fd013204249d3d24f9ea0 100644
--- a/chrome/browser/resources/chromeos/login/oobe.html
+++ b/chrome/browser/resources/chromeos/login/oobe.html
@@ -4,7 +4,11 @@
 <meta charset="utf-8">
 <meta name="google" value="notranslate">
 <title i18n-content="title"></title>
+<script src="chrome://oobe/polymer/platform/platform.js"></script>

[Nikita (slow), 2014/09/25 20:19:59]

I suggest having all Polymer specific include/script/link elements grouped
together. May as well add comment.

[dzhioev (left Google), 2014/09/26 22:56:11]

It is not possible now:
* custom element's CSS should be defined inside element definition.
* We should all <script src="..."> inclusions of local JS files to oobe.js.
Otherwise Grit will flatten them and they will not work.
* platform.js should be included first.

+<include src="oobe-screen.html">
+<include src="html-echo.html">
 <include src="login_resources.html">
+<link rel="stylesheet" href="roboto_font.css">

[Nikita (slow), 2014/09/25 20:19:59]

Do you think whether this will have perfomance effect on boot time?
Specifically for cases when font is not needed?

[dzhioev (left Google), 2014/09/26 22:56:11]

I doubt it.

 <link rel="stylesheet" href="accessibility_menu.css">
 <script src="chrome://oobe/oobe.js"></script>
 </head>