MD Settings: roll paper-submenu to fix double-tap bug when started open

MD Settings: roll paper-submenu to fix double-tap bug when started open

BUG=650951
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

[Dan Beam, 2016-10-14 02:30:41]

Description was changed from

==========
MD Settings: roll paper-submenu to fix double-tap bug when started open

R=dpapad@chromium.org
BUG=650951
==========

to

==========
MD Settings: roll paper-submenu to fix double-tap bug when started open

R=dpapad@chromium.org
BUG=650951
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

[dpapad, 2016-10-14 21:17:12]

https://codereview.chromium.org/2412343004/diff/1/third_party/polymer/v1_0/bo...
File third_party/polymer/v1_0/bower.json (right):

https://codereview.chromium.org/2412343004/diff/1/third_party/polymer/v1_0/bo...
third_party/polymer/v1_0/bower.json:52: "paper-menu":
"PolymerElements/paper-menu#opened-binding",
Is this better than updating our local patch file?

[Dan Beam, 2016-10-14 21:32:43]

Description was changed from

==========
MD Settings: roll paper-submenu to fix double-tap bug when started open

R=dpapad@chromium.org
BUG=650951
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

to

==========
MD Settings: roll paper-submenu to fix double-tap bug when started open

BUG=650951
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

[Dan Beam, 2016-10-14 21:32:44]

dbeam@chromium.org changed reviewers:
- dpapad@chromium.org

[Dan Beam, 2016-10-14 21:32:56]

stop looking for extra work ;)

https://codereview.chromium.org/2412343004/diff/1/third_party/polymer/v1_0/bo...
File third_party/polymer/v1_0/bower.json (right):

https://codereview.chromium.org/2412343004/diff/1/third_party/polymer/v1_0/bo...
third_party/polymer/v1_0/bower.json:52: "paper-menu":
"PolymerElements/paper-menu#opened-binding",
On 2016/10/14 21:17:12, dpapad wrote:
> Is this better than updating our local patch file?

eh, if we were actually to do this, i'd name it something generic like
"chrome-fork" or something.

this was just a WIP thing.  I didn't publish.

[dpapad, 2016-10-14 21:47:55]

On 2016/10/14 at 21:32:56, dbeam wrote:
> stop looking for extra work ;)
> 
>
https://codereview.chromium.org/2412343004/diff/1/third_party/polymer/v1_0/bo...
> File third_party/polymer/v1_0/bower.json (right):
> 
>
https://codereview.chromium.org/2412343004/diff/1/third_party/polymer/v1_0/bo...
> third_party/polymer/v1_0/bower.json:52: "paper-menu":
"PolymerElements/paper-menu#opened-binding",
> On 2016/10/14 21:17:12, dpapad wrote:
> > Is this better than updating our local patch file?
> 
> eh, if we were actually to do this, i'd name it something generic like
"chrome-fork" or something.
> 
> this was just a WIP thing.  I didn't publish.

Ah, I am sorry, habit.