Opened 11 years ago
Closed 11 years ago
#11261 closed defect (fixed)
dojox.form.manager._Mixin doesn't set radio button values properly
Reported by: | ben hockey | Owned by: | Eugene Lazutkin |
---|---|---|---|
Priority: | high | Milestone: | 1.5 |
Component: | DojoX Form | Version: | 1.5.0b2 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
using the test_Manager1.html test page try the following in the firebug console:
dijit.byId("form").formWidgetValue('w02', 'w02-1')
you'll see that the w02-2 radio button is unchecked but w02-1 does not get checked.
i also checked this in dojo 1.4.3 and this same problem exists in that version.
Attachments (2)
Change History (7)
Changed 11 years ago by
Attachment: | formAction.html added |
---|
Changed 11 years ago by
Attachment: | test_Manager2.html added |
---|
adaptation of dijit.form.Form unit test to help test some of dojox.form.Manager
comment:1 Changed 11 years ago by
i added a couple of files that might help with testing/identifying this problem. these are just an adaptation of the unit tests for dijit.form.Form. using these, i also found that checkboxes are also not working as expected.
comment:2 Changed 11 years ago by
Owner: | changed from dante to Eugene Lazutkin |
---|---|
Status: | new → assigned |
comment:3 Changed 11 years ago by
Milestone: | tbd → 1.5 |
---|---|
Status: | assigned → new |
comment:4 Changed 11 years ago by
Status: | new → assigned |
---|
It looks like dijit.form
widgets are far from stable, and not exactly regular. I need to special-case both dijit.form.CheckBox
and dijit.form.RadioButton
now. And replace attr()
with appropriate get()
and set()
calls. I am not sure how well it works with priorityChange
from #11284. And if all form widgets were converted to new get/set schema. If some dojox
widgets are still define attr()
instead of new API they'll break the form manager.
comment:5 Changed 11 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
formAction.html from dijit.form.Form unit tests