Skip to content
This repository has been archived by the owner on Dec 19, 2024. It is now read-only.

Two Way Slider #74

Closed
kishaningithub opened this issue Oct 5, 2015 · 11 comments
Closed

Two Way Slider #74

kishaningithub opened this issue Oct 5, 2015 · 11 comments

Comments

@kishaningithub
Copy link

It would be nice if this was a two way slider i.e. a range that the user can move the Min and Max Pin and it has two outputs and not just one.

Use Case:
-> Filter by "Price Range" in a shopping cart.

Some implementations
-> https://github.com/ewgenius/paper-interval-slider

I would be nice if polymer had this in its paper element set

@NicolasRannou
Copy link
Contributor

Not in the specs so unlikely to be supported until then:
https://www.google.com/design/spec/components/sliders.html

It would also be useful for medical imaging, along with vertical sliders.

Few months ago I played a bit with it:
http://nicolasrannou.github.io/paper-rangeslider/paper-rangeslider/demo/

But was waiting for the range slider to get more mature before going further...

@samccone
Copy link

samccone commented Oct 5, 2015

@blasten
Copy link
Contributor

blasten commented Oct 5, 2015

related: #8

As @nicolasgarnier pointed out, it's unlikely that paper-slider will support a two way slider as it's not in the spec. Also, good to know that there's a <paper-rangeslider>. It just needs to correct the progress bar as it seems to be off a few pixels.

@blasten blasten closed this as completed Oct 5, 2015
@samccone
Copy link

samccone commented Oct 5, 2015

as it's not in the spec

So to me, a range slider is a very common and useful UI component / pattern that plenty of apps use. Are we taking the approach that just because the spec does not explicitly define a component (or in this case a permutation of a component) we do not want to support/make it?

@blasten
Copy link
Contributor

blasten commented Oct 5, 2015

@samccone paper-* elements are specifically for material design elements. We could have an iron-range-slider for example.

@samccone
Copy link

samccone commented Oct 5, 2015

word :) sounds fair to me

@blasten
Copy link
Contributor

blasten commented Oct 5, 2015

:) that'd be a good primitive to have.

@opus1269
Copy link

opus1269 commented Oct 5, 2015

Wouldn't having it be an iron element make it more difficult since you couldn't leverage any of the paper features? Say you wanted a shadow or ripple, for example. I was thinking you could have another class of elements (that requires the paper elements) that would be for common material design based components that aren't part of the spec.

@blasten
Copy link
Contributor

blasten commented Oct 7, 2015

A quick update on this request. After talking to folks, material design may support range sliders in the upcoming months, so I'm reopening this feature request.

@NicolasRannou
Copy link
Contributor

awesome! main challenge is to make is touch devices friendly, that is what I was experimenting with even if my implementation is buggy :)

@blasten
Copy link
Contributor

blasten commented Jan 28, 2016

I will close this issue and follow up in #69

@blasten blasten closed this as completed Jan 28, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants