CheckBox: get("value") return code is strange

[frostmourn]

I use dijit.form.CheckBox? getValue method and found it is strange.When the checkbox is checked, getValue method returns "on" , and when it is not checked, it returns false. I think it's not a good design.By the way , when I use this code:

var value = dojo.byId("checkboxID").value;

or

var value = dojo.byId("checkboxID").checked;

the value is undefined. It's not convenient for users.

[bill]

Yes, the current behavior is the compromise of a long discussion... the issue is that:

• unlike plain <input>'s, HTML <input type=checkbox> and dijit.form.CheckBox widgets have both a string value attribute (by default == "on"), and a boolean checked attribute (which reflects whether or not the checkbox is checked).
• but dojo users wanted getValue() to "work uniformly" across the form widgets, meaning that code could query the "value" of all the widgets inside a form w/out having a special branch for a dijit.form.CheckBox
• all changes made after 1.0 needed to be backwards compatible

I can't think of any way to change this that would make it "better" in most people's eyes, except maybe returning null or "" rather than false. What change did you have in mind?

[Douglas Hays]

An added design point was the need for widget.attr('value', widget.attr('value')) to work.

[bill]

Marking this as fixed in 2.0 because ​https://github.com/ibm-js/deliteful/blob/master/Checkbox.js doesn't have that goofy code conflating the checked and value attributes.