4
edits
DOM/Web Forms 2.0: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 71: | Line 71: | ||
** disabled state when parent <fieldset> is disabled | ** disabled state when parent <fieldset> is disabled | ||
** XBL extension for <input> elements with an associated <datalist> | ** XBL extension for <input> elements with an associated <datalist> | ||
** The XBL stuff is mostly plug & play. Most of the work here will involve tweaking the new XUL elements to accommodate WF2. | |||
** I need to raise a series of bugs to get XUL up to speed. | |||
* <b>NodeLists</b> | * <b>NodeLists</b> | ||
** The forms/elements/labels/selectedOptions DOM properties return NodeLists. NodeLists are live. How do we fake these using JavaScript? Do we want to fake them with JavaScript? These properties will probably be slow if implemented in JavaScript. | ** The forms/elements/labels/selectedOptions DOM properties return NodeLists. NodeLists are live. How do we fake these using JavaScript? Do we want to fake them with JavaScript? These properties will probably be slow if implemented in JavaScript. | ||
| Line 77: | Line 79: | ||
** validation - should not submit invalid forms. How do we hijack submission and yet allow user scripts to trap the "submit" event also? | ** validation - should not submit invalid forms. How do we hijack submission and yet allow user scripts to trap the "submit" event also? | ||
** There are various new formats for form submission (phase 3) | ** There are various new formats for form submission (phase 3) | ||
** Trapping form submission - I'm not sure how to do this. Presumably I can just trap onsubmit? | |||
** If we support multiple bindings of elements to forms then we will need to serialize the form ourselves prior to submission. | |||
== Technologies == | == Technologies == | ||