Fetch and actually set prefs (using chrome.send for now).

chrome/browser/resources/settings/prefs/prefs.html

Index: chrome/browser/resources/settings/prefs/prefs.html
diff --git a/chrome/browser/resources/settings/prefs/prefs.html b/chrome/browser/resources/settings/prefs/prefs.html
index c2e6dd57131496c735ab93b1a9ead6826b2cd3b5..157d3c2b15d074ea29d2bd3442aac32d032c5f17 100644
--- a/chrome/browser/resources/settings/prefs/prefs.html
+++ b/chrome/browser/resources/settings/prefs/prefs.html
@@ -1,4 +1,6 @@
 <link rel="import" href="chrome://resources/polymer/polymer/polymer.html">
+<script src="chrome://resources/js/assert.js"></script>

[Kyle Horimoto, 2015/03/19 22:42:11]

Using a <script> instead of a <link rel="import"> will NOT dedupe the request,
right? So, if we include the same script multiple times, bad stuff will happen?
We should probably figure out a centralized way to do this instead of doing it
on an individual element.

[Jeremy Klein, 2015/03/19 23:04:21]

I'm glad you brought this up because I actually meant to ask about it! In these
cases, it isn't actually a big deal to duplicate the scripts, but I do agree
that it would be cool to take advantage of the deduping that imports give us.
This will basically mean wrapping assert.js and cr.js in assert.html and cr.html
with only a script tag. I'm actually cool with this and will go ahead and do it
as long as there aren't any strong objections. There is precedent for this in
files like this:

https://code.google.com/p/chromium/codesearch#chromium/src/third_party/polyme...

I think it's a nice pattern to follow for dependency management.

+<script src="chrome://resources/js/cr.js"></script>
 
 <polymer-element name="cr-settings-prefs">
   <script src="prefs.js"></script>