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

Binding to input type=range does not work in IE 11 #416

Closed
hpoul opened this issue Feb 5, 2014 · 4 comments
Closed

Binding to input type=range does not work in IE 11 #416

hpoul opened this issue Feb 5, 2014 · 4 comments

Comments

@hpoul
Copy link

hpoul commented Feb 5, 2014

when binding to a range input element, it is not (live) updated in IE 11
tested with 11.0.9600.16384 - just trying out the example can reproduce the problem: http://www.polymer-project.org/getting-started.html -> "Binding between components and native elements" - when moving the slider in IE, the age in the text is not updated at all. Works on all other browsers though.

is this a known issue with IE, or a bug?

@rafaelw
Copy link
Contributor

rafaelw commented Feb 5, 2014

Short answer: use

Long answer: IE has non-spec behavior which means that it "sanitizes"
attribute values. In this case, it thinks that because type is "range",
value should always be an integer, so it throws away the binding text.

In general, binding to an attribute can also be done with a preceding
underscore for this and a few other reasons.

On Wed, Feb 5, 2014 at 7:09 AM, Herbert Poul notifications@github.comwrote:

when binding to a range input element, it is not (live) updated in IE 11
tested with 11.0.9600.16384 - just trying out the example can reproduce
the problem: http://www.polymer-project.org/getting-started.html ->
"Binding between components and native elements" - when moving the slider
in IE, the age in the text is not updated at all. Works on all other
browsers though.

is this a known issue with IE, or a bug?


Reply to this email directly or view it on GitHubhttps://github.com//issues/416
.

@ebidel
Copy link
Contributor

ebidel commented Feb 5, 2014

@hpoul
Copy link
Author

hpoul commented Feb 11, 2014

thanks for the fast response.. feeling a bit dumb, that i didn't read that far down in the documentation, but i've now tried that approach and basically modified the example from 'getting started' to:

<input id="ageInput" type="range" _value="{{age}}">

unfortunately this didn't change anything for me, the initial value seems to be correct, but when moving the slider the underlying property is not changed.. but: it works the other way around, when i'm changing this.age in javascript, the slider is updated.

am i still doing something wrong here? maybe someone could fix the example, so it also works in IE11?

(i've tried it with a fresh install using bower - bower_components/polymer/polymer.js contains version: 0.1.4)

@rafaelw
Copy link
Contributor

rafaelw commented Feb 11, 2014

Turns out IE doesn't fire 'input' events for range types. Boo, IE.

Fixed here: googlearchive/NodeBind@31044dd

Thanks for persisting with the bug report.

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