Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bindings on a range input not working well in google chrome #182

Closed
gunn opened this issue Jun 13, 2013 · 3 comments
Closed

Bindings on a range input not working well in google chrome #182

gunn opened this issue Jun 13, 2013 · 3 comments

Comments

@gunn
Copy link

gunn commented Jun 13, 2013

I want to dynamically set a slider's min and max attributes and expect it's slider position to update in response.

Here's an example: http://jsbin.com/uqifox/3/edit
And here's it behaving after a hacky workaround: http://jsbin.com/uqifox/2/edit

Note that I have to explicitly set the slider's value twice:

this.$.slider.value = 1;
this.$.slider.value = 0;
@sjmiles
Copy link
Contributor

sjmiles commented Jun 13, 2013

I suspect your problem is with <input> and not with Polymer. It looks to me like <input> doesn't update it's value position when you change min or max.

This may be a bug in Blink.

I also believe that the 'set the value twice' effect is only because the element is optimized to do nothing if the value hasn't actually changed.

@gunn
Copy link
Author

gunn commented Jun 13, 2013

Yes I'm sure that's right, I thought I'd add it here to document it and incase it was part of something polymer could work around.

Works fine in safari by the way. Is it worth reporting to the chrome team?

@dfreedm
Copy link
Member

dfreedm commented Jul 24, 2013

This was a blink bug that is fixed in Chrome 29: http://crbug.com/249909

@dfreedm dfreedm closed this as completed Jul 24, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants