[Polymer] update third_party polymer

[Polymer] update third_party polymer

This CL updates the third party Polymer JavaScript library,
with the addition of a patch for neon-animated pages.

The patch change is shown in the chromium.patch file within
this CL.  It comes from
https://github.com/PolymerElements/neon-animation/pull/149

BUG=600887
TBR=dzhioev@chromium.org
NOPRESUBMIT=true
^ because crisper files are machine generated and do not obey
the 80 character limit.

Committed: https://crrev.com/617644937cf254786783bc59b975613ea7e274fa
Cr-Commit-Position: refs/heads/master@{#389329}

[dschuyler, 2016-04-21 01:17:18]

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

[dschuyler, 2016-04-21 01:17:19]

Testing done:
- this fixes my issue with subpages expanding
- this fixes the redraw flash going to chrome://md-settings/searchEngines
- this fixes the dialog centering while the window is resizing
- closure compiles without error

[Dan Beam, 2016-04-21 18:48:26]

surely there must be some BUG= to put here?

also, were did we find the chromium.patch diff?  is it something the polymer
team wants?  because it seems like it could have unintended side effects
maybe...

[dschuyler, 2016-04-21 18:51:11]

Description was changed from

==========
[Polymer] update third_party polymer

This CL updates the third party Polymer JavaScript library,
with the addition of a patch for neon-animated pages.

The patch change is shown in the chromium.patch file within
this CL.

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

to

==========
[Polymer] update third_party polymer

This CL updates the third party Polymer JavaScript library,
with the addition of a patch for neon-animated pages.

The patch change is shown in the chromium.patch file within
this CL.  It comes from 
https://github.com/PolymerElements/neon-animation/pull/149

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

[dschuyler, 2016-04-21 18:56:04]

Description was changed from

==========
[Polymer] update third_party polymer

This CL updates the third party Polymer JavaScript library,
with the addition of a patch for neon-animated pages.

The patch change is shown in the chromium.patch file within
this CL.  It comes from 
https://github.com/PolymerElements/neon-animation/pull/149

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

to

==========
[Polymer] update third_party polymer

This CL updates the third party Polymer JavaScript library,
with the addition of a patch for neon-animated pages.

The patch change is shown in the chromium.patch file within
this CL.  It comes from 
https://github.com/PolymerElements/neon-animation/pull/149

BUG=600887
==========

[dschuyler, 2016-04-21 18:57:27]

On 2016/04/21 18:48:26, Dan Beam wrote:
> surely there must be some BUG= to put here?
> 
> also, were did we find the chromium.patch diff?  is it something the polymer
> team wants?  because it seems like it could have unintended side effects
> maybe...

I've put the bug about the window resizing in the CL
description. I also made a note of where the patch
came from in the description.

[Dan Beam, 2016-04-21 20:33:36]

https://codereview.chromium.org/1901343004/diff/1/third_party/polymer/v1_0/co...
File
third_party/polymer/v1_0/components-chromium/iron-dropdown/compiled_resources2.gyp
(right):

https://codereview.chromium.org/1901343004/diff/1/third_party/polymer/v1_0/co...
third_party/polymer/v1_0/components-chromium/iron-dropdown/compiled_resources2.gyp:14:
},
can we fix the sorting issues before landing?

[dschuyler, 2016-04-21 23:07:07]

Patchset #2 (id:20001) has been deleted

[dschuyler, 2016-04-21 23:09:00]

On 2016/04/21 20:33:36, Dan Beam wrote:
>
https://codereview.chromium.org/1901343004/diff/1/third_party/polymer/v1_0/co...
> File
>
third_party/polymer/v1_0/components-chromium/iron-dropdown/compiled_resources2.gyp
> (right):
> 
>
https://codereview.chromium.org/1901343004/diff/1/third_party/polymer/v1_0/co...
>
third_party/polymer/v1_0/components-chromium/iron-dropdown/compiled_resources2.gyp:14:
> },
> can we fix the sorting issues before landing?

The generated files should have their contents sorted
correctly now.  The sort order within 
iron-menu-behavior/compiled_resources2.gyp is
changing because it was incorrect.

[dschuyler, 2016-04-21 23:09:09]

https://codereview.chromium.org/1901343004/diff/1/third_party/polymer/v1_0/co...
File
third_party/polymer/v1_0/components-chromium/iron-dropdown/compiled_resources2.gyp
(right):

https://codereview.chromium.org/1901343004/diff/1/third_party/polymer/v1_0/co...
third_party/polymer/v1_0/components-chromium/iron-dropdown/compiled_resources2.gyp:14:
},
On 2016/04/21 20:33:36, Dan Beam wrote:
> can we fix the sorting issues before landing?

Done.

[Dan Beam, 2016-04-22 02:29:19]

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

[Dan Beam, 2016-04-22 02:29:21]

lgtm i guess, but i'd prefer to just wait for the fix to be agreed upon by the
polymer team rather than added to chromium.patch

+michaelpg@ as well

[michaelpg, 2016-04-22 18:48:47]

On 2016/04/22 02:29:21, Dan Beam wrote:
> lgtm i guess, but i'd prefer to just wait for the fix to be agreed upon by the
> polymer team rather than added to chromium.patch
> 
> +michaelpg@ as well

thx, we talked about this at the standup and it looks like a (different) patch
landed to address the issue -- if it does fix dschuyler's issue, yay!

[dschuyler, 2016-04-22 19:30:54]

On 2016/04/22 18:48:47, michaelpg wrote:
> On 2016/04/22 02:29:21, Dan Beam wrote:
> > lgtm i guess, but i'd prefer to just wait for the fix to be agreed upon by
the
> > polymer team rather than added to chromium.patch
> > 
> > +michaelpg@ as well
> 
> thx, we talked about this at the standup and it looks like a (different) patch
> landed to address the issue -- if it does fix dschuyler's issue, yay!

Patch 2 has the new Polymer update and the patch removed
from chromium.patch.

[dschuyler, 2016-04-22 19:31:57]

On 2016/04/22 19:30:54, dschuyler wrote:
> On 2016/04/22 18:48:47, michaelpg wrote:
> > On 2016/04/22 02:29:21, Dan Beam wrote:
> > > lgtm i guess, but i'd prefer to just wait for the fix to be agreed upon by
> the
> > > polymer team rather than added to chromium.patch
> > > 
> > > +michaelpg@ as well
> > 
> > thx, we talked about this at the standup and it looks like a (different)
patch
> > landed to address the issue -- if it does fix dschuyler's issue, yay!
> 
> Patch 2 has the new Polymer update and the patch removed
> from chromium.patch.

Whoops, I meant the latest patch, patch 3.

[michaelpg, 2016-04-22 19:34:05]

lgtm. I would TBR dzhioev@ since I don't know when he'll be in. I'll also put up
a CL to add myself as an OWNER for third_party/web-animations-js.

[dschuyler, 2016-04-22 20:31:03]

Description was changed from

==========
[Polymer] update third_party polymer

This CL updates the third party Polymer JavaScript library,
with the addition of a patch for neon-animated pages.

The patch change is shown in the chromium.patch file within
this CL.  It comes from 
https://github.com/PolymerElements/neon-animation/pull/149

BUG=600887
==========

to

==========
[Polymer] update third_party polymer

This CL updates the third party Polymer JavaScript library,
with the addition of a patch for neon-animated pages.

The patch change is shown in the chromium.patch file within
this CL.  It comes from 
https://github.com/PolymerElements/neon-animation/pull/149

BUG=600887
TBR=dzhioev@chromium.org
==========

[dschuyler, 2016-04-22 23:20:06]

The CQ bit was checked by dschuyler@chromium.org

[dschuyler, 2016-04-22 23:20:07]

The patchset sent to the CQ was uploaded after l-g-t-m from dbeam@chromium.org
Link to the patchset: https://codereview.chromium.org/1901343004/#ps60001
(title: "new pull")

[commit-bot: I haz the power, 2016-04-22 23:20:37]

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

[commit-bot: I haz the power, 2016-04-22 23:35:49]

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

[commit-bot: I haz the power, 2016-04-22 23:35:51]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[dschuyler, 2016-04-23 00:40:33]

Description was changed from

==========
[Polymer] update third_party polymer

This CL updates the third party Polymer JavaScript library,
with the addition of a patch for neon-animated pages.

The patch change is shown in the chromium.patch file within
this CL.  It comes from 
https://github.com/PolymerElements/neon-animation/pull/149

BUG=600887
TBR=dzhioev@chromium.org
==========

to

==========
[Polymer] update third_party polymer

This CL updates the third party Polymer JavaScript library,
with the addition of a patch for neon-animated pages.

The patch change is shown in the chromium.patch file within
this CL.  It comes from 
https://github.com/PolymerElements/neon-animation/pull/149

BUG=600887
TBR=dzhioev@chromium.org
NOPRESUBMIT=true 
^ because crisper files are machine generated and do not obey
the 80 character limit.
==========

[dschuyler, 2016-04-23 00:40:44]

The CQ bit was checked by dschuyler@chromium.org

[commit-bot: I haz the power, 2016-04-23 00:41:06]

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

[commit-bot: I haz the power, 2016-04-23 00:42:40]

Description was changed from

==========
[Polymer] update third_party polymer

This CL updates the third party Polymer JavaScript library,
with the addition of a patch for neon-animated pages.

The patch change is shown in the chromium.patch file within
this CL.  It comes from 
https://github.com/PolymerElements/neon-animation/pull/149

BUG=600887
TBR=dzhioev@chromium.org
NOPRESUBMIT=true 
^ because crisper files are machine generated and do not obey
the 80 character limit.
==========

to

==========
[Polymer] update third_party polymer

This CL updates the third party Polymer JavaScript library,
with the addition of a patch for neon-animated pages.

The patch change is shown in the chromium.patch file within
this CL.  It comes from 
https://github.com/PolymerElements/neon-animation/pull/149

BUG=600887
TBR=dzhioev@chromium.org
NOPRESUBMIT=true 
^ because crisper files are machine generated and do not obey
the 80 character limit.
==========

[commit-bot: I haz the power, 2016-04-23 00:42:42]

Committed patchset #3 (id:60001)

[commit-bot: I haz the power, 2016-04-23 00:45:04]

Description was changed from

==========
[Polymer] update third_party polymer

This CL updates the third party Polymer JavaScript library,
with the addition of a patch for neon-animated pages.

The patch change is shown in the chromium.patch file within
this CL.  It comes from 
https://github.com/PolymerElements/neon-animation/pull/149

BUG=600887
TBR=dzhioev@chromium.org
NOPRESUBMIT=true 
^ because crisper files are machine generated and do not obey
the 80 character limit.
==========

to

==========
[Polymer] update third_party polymer

This CL updates the third party Polymer JavaScript library,
with the addition of a patch for neon-animated pages.

The patch change is shown in the chromium.patch file within
this CL.  It comes from
https://github.com/PolymerElements/neon-animation/pull/149

BUG=600887
TBR=dzhioev@chromium.org
NOPRESUBMIT=true
^ because crisper files are machine generated and do not obey
the 80 character limit.

Committed: https://crrev.com/617644937cf254786783bc59b975613ea7e274fa
Cr-Commit-Position: refs/heads/master@{#389329}
==========

[commit-bot: I haz the power, 2016-04-23 00:45:06]

Patchset 3 (id:??) landed as
https://crrev.com/617644937cf254786783bc59b975613ea7e274fa
Cr-Commit-Position: refs/heads/master@{#389329}