[Polymer] Roll polymer to latest version

Roll polymer to latest version.

Done by running third_party/polymer/v1_0/reproduce.sh.

Fixes compile error found in https://codereview.chromium.org/1521433002/

BUG=none

Committed: https://crrev.com/2c36bcb1978cbdf4702b378bbf230f0f373a6340
Cr-Commit-Position: refs/heads/master@{#369338}

[imcheng, 2016-01-06 01:49:11]

Description was changed from

==========
roll polymer

BUG=
==========

to

==========
Roll polymer to latest version.

Done by running third_party/polymer/v1_0/reproduce.sh.

Fixes compile error found in https://codereview.chromium.org/1521433002/

BUG=none
==========

[imcheng, 2016-01-06 01:56:46]

imcheng@chromium.org changed reviewers:
+ dbeam@chromium.org

[imcheng, 2016-01-06 01:56:47]

Dan: PTAL thanks!

[imcheng, 2016-01-06 19:24:38]

Uploaded new PS with use of --script-in-head=false and updated grdp, PTAL

[Dan Beam, 2016-01-06 22:12:31]

lgtm let's see how this goes (feel free to try any of the pages you can,
including yours, to make sure they still look right)

[imcheng, 2016-01-06 23:12:37]

looks good on downloads and media-router

[imcheng, 2016-01-07 21:23:15]

Ok I think I found out what is causing the test failure. tldr: vulcanized code
doesn't play well with importing extra Polymer libraries on the side.

PolymerTestBase imports iron-test-helpers.html, which was changed to use HTML
imports instead of script src. This meant it also had to import polymer.html if
it thinks it has not been imported yet. The problem is vulcanization gets rid of
all the HTML imports in md downloads - so when it comes to load
iron-test-helpers.html, it will "re-import" polymer.html - which causes
duplicate registration of elements (which emits the error message).

But let's say we ignored the exception. There's still a problem because
reimporting polymer.html also resets the existing Polymer object (e.g.,
Polymer.IronSelection which was added when loading md downloads, is now gone),
which will cause the test setup to fail.

I am not sure how to fix this but I do have a couple of options in mind:

1) use the regular version of md downloads instead of vulcanized version in
test. In general, don't use vulcanized version in PolymerTest because the
infrastructure doesn't support it. One concern is that we no longer test the
vulcanized version, which is supposed to be used in production.

2) don't import iron-test-helpers.html in md downloads test. This will come back
to bite us if we do need to import it in the future.

Any thoughts or ideas?

[imcheng, 2016-01-12 18:34:40]

Ping! Please let me know how I can help to move forward with this.

[michaelpg, 2016-01-12 18:37:48]

On 2016/01/12 18:34:40, imcheng1 wrote:
> Ping! Please let me know how I can help to move forward with this.

looking

[michaelpg, 2016-01-12 19:19:01]

On 2016/01/12 18:37:48, michaelpg wrote:
> On 2016/01/12 18:34:40, imcheng1 wrote:
> > Ping! Please let me know how I can help to move forward with this.
> 
> looking

see https://codereview.chromium.org/1575953004/ for proposed fix. Seems to work
with this patch.

[imcheng, 2016-01-13 21:44:42]

The CQ bit was checked by imcheng@chromium.org

[commit-bot: I haz the power, 2016-01-13 21:46:44]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1561893002/80001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1561893002/80001

[commit-bot: I haz the power, 2016-01-13 23:55:20]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-01-13 23:55:20]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_TIMED_OUT, no build URL)
  mac_chromium_rel_ng on tryserver.chromium.mac (JOB_TIMED_OUT, no build URL)

[imcheng, 2016-01-14 01:27:23]

The CQ bit was checked by imcheng@chromium.org

[commit-bot: I haz the power, 2016-01-14 01:31:10]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1561893002/80001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1561893002/80001

[commit-bot: I haz the power, 2016-01-14 03:41:49]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-01-14 03:41:50]

Try jobs failed on following builders:
  android_compile_dbg on tryserver.chromium.android (JOB_TIMED_OUT, no build
URL)

[imcheng, 2016-01-14 05:28:03]

The CQ bit was checked by imcheng@chromium.org

[commit-bot: I haz the power, 2016-01-14 05:29:23]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1561893002/80001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1561893002/80001

[commit-bot: I haz the power, 2016-01-14 05:36:44]

Description was changed from

==========
Roll polymer to latest version.

Done by running third_party/polymer/v1_0/reproduce.sh.

Fixes compile error found in https://codereview.chromium.org/1521433002/

BUG=none
==========

to

==========
Roll polymer to latest version.

Done by running third_party/polymer/v1_0/reproduce.sh.

Fixes compile error found in https://codereview.chromium.org/1521433002/

BUG=none
==========

[commit-bot: I haz the power, 2016-01-14 05:36:45]

Committed patchset #5 (id:80001)

[commit-bot: I haz the power, 2016-01-14 05:37:47]

Description was changed from

==========
Roll polymer to latest version.

Done by running third_party/polymer/v1_0/reproduce.sh.

Fixes compile error found in https://codereview.chromium.org/1521433002/

BUG=none
==========

to

==========
Roll polymer to latest version.

Done by running third_party/polymer/v1_0/reproduce.sh.

Fixes compile error found in https://codereview.chromium.org/1521433002/

BUG=none

Committed: https://crrev.com/2c36bcb1978cbdf4702b378bbf230f0f373a6340
Cr-Commit-Position: refs/heads/master@{#369338}
==========

[commit-bot: I haz the power, 2016-01-14 05:37:48]

Patchset 5 (id:??) landed as
https://crrev.com/2c36bcb1978cbdf4702b378bbf230f0f373a6340
Cr-Commit-Position: refs/heads/master@{#369338}