-
Notifications
You must be signed in to change notification settings - Fork 27.4k
checkbox: ngTrueValue/ngFalseValue not working properly with ngRequired #4970
Comments
Nice catch! |
http://jsfiddle.net/cHCdu/18/ might be a slightly clearer reproduction. A fix should be pretty simple for this, but might hurt performance. I think I've mentioned elsewhere that there can be variations on the semantic meaning of a "required" checkbox, it doesn't necessarily always mean that it is required to be "checked" (for instance, in some cases, an indeterminate checkbox value might not be considered to be an entered value, and should not get past required field validation). So this problem can get a bit more complicated, but maybe a short term fix would be just to add a call to |
Actually, a call to Since it's kind of a breaking change with all of the review comments addressed, it's unlikely to be merged in time for 1.2.8 though. |
+1. Would love to see this make it's way in some form of 1.2.x as it looks like I will not be able to drop IE8 in the near future. |
the implementation is a feature so we can't add it to 1.2.x, but it's a pretty trivial feature so you could apply it to v1.2.x manually, for sure |
Thanks for the prompt reply, and thanks, I am currently going with a manual workaround. |
This has been fixed in master: 3e51b84 |
This is my dynamic generated Check box list. In this check box list we click on any one, it display checked. But actually its attribute "checked" is none. var ch =$(checkbox).attr('checked'); return ch = "Undefined" |
Actually doesn't work at all. Please see: http://jsfiddle.net/cHCdu/11/
The text was updated successfully, but these errors were encountered: