#6192 closed enhancement (wontfix)
make dijit.form.Form more useful
Reported by: | alex | Owned by: | |
---|---|---|---|
Priority: | high | Milestone: | 1.4 |
Component: | Dijit - Form | Version: | 1.1b1 |
Keywords: | form, dijit | Cc: | alex, dante |
Blocked By: | Blocking: |
Description (last modified by )
today dijit.form.Form doesn't handle some straight-forward use-cases. For instance:
- addChild() doesn't work
- handling of native HTML input types is feeble to non-existant
- form.Form can't auto-generate fieldsets from groups of item/label/required pairs/objects
- form.Form doesn't handle automatic XHR-ing of form data
- there's no dojo.data integration
Change History (6)
comment:1 Changed 12 years ago by
Description: | modified (diff) |
---|
comment:2 Changed 12 years ago by
Summary: | make dijit.form.Form actually useful in the real world → make dijit.form.Form more useful |
---|
comment:3 Changed 12 years ago by
Description: | modified (diff) |
---|
comment:4 Changed 12 years ago by
Milestone: | 1.2 → 1.4 |
---|
Owner for dijit.Form definitely appreciated... we are kind-of waiting on Joose but he's been busy recently; he said he would hopefully have more time in the summer, IIRC, which is coming soon.
addChild() doesn't work
I'm not sure what addChild() would mean on free-form HTML like a form.
handling of native HTML input types is feeble to non-existant
Dup of #4408
Anyway, this meta-ticket needs to be split into individual tickets and then can consider each one.
comment:5 Changed 11 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
I'm going to close this ticket. It's too general. #4408 addresses the second issue, and the other issues need to be filed as separate tickets (although really, we need a volunteer to implement stuff like dojo.data integration.
comment:6 Changed 9 years ago by
Component: | Dijit → Dijit - Form |
---|
This one needs an owner, Perhaps Nathan or Sam are interested?