[MD settings] support RTL in paper-slider

[MD settings] support RTL in paper-slider

This CL change the third_party/polymer code to support rtl in
paper-slider by mirroring the control and input in rtl locales.

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

[dschuyler, 2017-04-05 22:49:51]

Description was changed from

==========
[MD settings] support RTL in paper-slider

This CL change the third_party/polymer code to support rtl in
paper-slider by mirroring the control and input in rtl locales.

BUG=696437
==========

to

==========
[MD settings] support RTL in paper-slider

This CL change the third_party/polymer code to support rtl in
paper-slider by mirroring the control and input in rtl locales.

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

[dschuyler, 2017-04-05 22:49:53]

The CQ bit was checked by dschuyler@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-04-05 22:50:34]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[dschuyler, 2017-04-05 22:53:35]

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

[dschuyler, 2017-04-05 22:53:36]

There is a PR for this at
https://github.com/PolymerElements/paper-slider/pull/181

[tommycli, 2017-04-05 23:09:16]

On 2017/04/05 22:53:36, dschuyler wrote:
> There is a PR for this at
> https://github.com/PolymerElements/paper-slider/pull/181

I thought our standard procedure was to get the pull request accepted, then do a
polymer roll after they issued a new version?

Did we change our standard to make changes locally ahead of pull request
acceptance?

[dschuyler, 2017-04-05 23:21:00]

On 2017/04/05 23:09:16, tommycli wrote:
> On 2017/04/05 22:53:36, dschuyler wrote:
> > There is a PR for this at
> > https://github.com/PolymerElements/paper-slider/pull/181
> 
> I thought our standard procedure was to get the pull request accepted, then do
a
> polymer roll after they issued a new version?
> 
> Did we change our standard to make changes locally ahead of pull request
> acceptance?

Yes, that was a topic from a team stand-up some time ago (unless it changed back
again).

[dschuyler, 2017-04-05 23:33:28]

On 2017/04/05 23:21:00, dschuyler wrote:
> On 2017/04/05 23:09:16, tommycli wrote:
> > On 2017/04/05 22:53:36, dschuyler wrote:
> > > There is a PR for this at
> > > https://github.com/PolymerElements/paper-slider/pull/181
> > 
> > I thought our standard procedure was to get the pull request accepted, then
do
> a
> > polymer roll after they issued a new version?
> > 
> > Did we change our standard to make changes locally ahead of pull request
> > acceptance?
> 
> Yes, that was a topic from a team stand-up some time ago (unless it changed
back
> again).

If Polymer responds to the PR relatively soon then we can go with the PR. I'll
check on that (give me a day or so).

[commit-bot: I haz the power, 2017-04-06 00:20:55]

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

[commit-bot: I haz the power, 2017-04-06 00:20:56]

Dry run: This issue passed the CQ dry run.

[dschuyler, 2017-04-07 19:10:39]

On 2017/04/05 23:33:28, dschuyler wrote:
> On 2017/04/05 23:21:00, dschuyler wrote:
> > On 2017/04/05 23:09:16, tommycli wrote:
> > > On 2017/04/05 22:53:36, dschuyler wrote:
> > > > There is a PR for this at
> > > > https://github.com/PolymerElements/paper-slider/pull/181
> > > 
> > > I thought our standard procedure was to get the pull request accepted,
then
> do
> > a
> > > polymer roll after they issued a new version?
> > > 
> > > Did we change our standard to make changes locally ahead of pull request
> > > acceptance?
> > 
> > Yes, that was a topic from a team stand-up some time ago (unless it changed
> back
> > again).
> 
> If Polymer responds to the PR relatively soon then we can go with the PR. I'll
> check on that (give me a day or so).

The Polymer PR went through (https://codereview.chromium.org/2801193002/).
I'll close this one.