-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Bound boolean isn't set from true to false when radio button is unchecked #291
Comments
Functionality of input type radio came up before and led to us making an example that works with polymer-selector. It's available at the bottom of the example file here: https://github.com/Polymer/polymer-elements/blob/master/polymer-selector/index.html |
@sethladd and I also came up with http://jsbin.com/iXuSOCO/2/edit as a raw radio button solution. |
Thanks guys, those are good workarounds. I was hoping that this bug report is a fine-grained and distilled repro of what is possibly indicative of a bug. Does HTML fire a changed event when a radio button goes from true to false? I'll need to investigate. |
Re: the change event, I don't think so. I'll let @rafaelw weigh in on supporting this better in Node.bind. On Sep 24, 2013, at 6:11 PM, Seth Ladd [email protected] wrote: Thanks guys, those are good workarounds. I was hoping that this bug report Does HTML fire a changed event when a radio button goes from true to false? — |
Some observations... I think it's NodeBind.js getAssociatedRadioButtons() that prevents the radio button from being checked because:
Hope this helps. |
Thanks Peter. Someone on the list brought up the getAssociatedRadioButtons diagnosis as well. |
Yup. getAssociatedRadioButtons needed to be tolerant of associated radio buttons within a ShadowRoot. Fixed here: googlearchive/NodeBind@9978535 |
Very cool, thanks Raf! |
Going from false to true sets the bound boolean, but going from true to false does not set the bound boolean back to false.
Here's the test:
/cc @ebidel
The text was updated successfully, but these errors were encountered: