Import Polymer 0.8 and several key elements.

third_party/polymer/v0_8/reproduce.sh

Index: third_party/polymer/v0_8/reproduce.sh
diff --git a/third_party/polymer/v0_8/reproduce.sh b/third_party/polymer/v0_8/reproduce.sh
new file mode 100755
index 0000000000000000000000000000000000000000..d46a45864415afbca541d2441052dc87d186f456
--- /dev/null
+++ b/third_party/polymer/v0_8/reproduce.sh
@@ -0,0 +1,42 @@
+#!/bin/bash
+
+# Copyright 2014 The Chromium Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+# Reproduces the content of 'components' and 'components-chromium' using the
+# list of dependencies from 'bower.json'. Downloads needed packages and makes
+# Chromium specific modifications. To launch the script you need 'bower' and
+# 'vulcanize' to be install in your system.
+
+# IMPORTANT NOTE: The new vulcanize must be installed from
+# https://github.com/Polymer/vulcanize/releases since it isn't on npm yet.
+
+set -e
+
+cd "$(dirname "$0")"
+
+rm -rf components components-chromium
+
+bower install
+
+# These components are deprecated or needed only for demos.
+rm -rf components/{iron-component-page,webcomponentsjs}
+
+# Make checkperms.py happy.
+find components/iron-selector -type f -exec chmod -x {} \;
+chmod +x components/polymer/build.bat
+
+# Remove carriage returns to make CQ happy.
+find components -type f \( -name \*.html -o -name \*.css -o -name \*.js\
+  -o -name \*.md -o -name \*.sh -o -name \*.json -o -name \*.gitignore \)\
+  -print0 | xargs -0 sed -i -e $'s/\r$//g'
+
+./extract_inline_scripts.sh components components-chromium
+

[michaelpg, 2015/04/25 02:38:04]

does chromium.patch no longer apply because we vulcanize?

[Jeremy Klein, 2015/04/25 19:54:07]

I think it just doesn't apply because afaict the line that the patch was
removing doesn't exist anymore. I couldn't find any instances of HTML elements
that would cause the same problem in js comments in 0.8.

+# Actually fully vulcanize polymer.html to avoid needing to serve each file in
+# the library separately.
+vulcanize --inline-scripts components/polymer/polymer.html > components-chromium/polymer/polymer.html
+crisper --source components-chromium/polymer/polymer.html\

[michaelpg, 2015/04/25 02:38:04]

another dependency? should we call it out in the header like we do with
vulcanize?

[Jeremy Klein, 2015/04/25 19:54:07]

Good call. Done. FYI, crisper is what splits out the js from the html. That
piece of vulcanize was broken out into its own tool.

+  --html "components-chromium/polymer/polymer.html"\
+  --js "components-chromium/polymer/polymer.js"