Confirmed users
146
edits
DOM/Web Forms 2.0: Difference between revisions
m
→Possible Approaches
| Line 29: | Line 29: | ||
== Possible Approaches == | == Possible Approaches == | ||
In the spirit of TIMTOWTDI, | In the spirit of TIMTOWTDI, we'd like to consider various ways of implementing WF2, using the best tools available. | ||
=== Javascript and XBL === | === Javascript and XBL === | ||
| Line 47: | Line 47: | ||
* Though we should be able to do various html:input types this way, there are unresolved questions: | * Though we should be able to do various html:input types this way, there are unresolved questions: | ||
** How do we tell nsCSSFrameConstructor, for these inputs, to accept XBL-based form controls? | ** How do we tell nsCSSFrameConstructor, for these inputs, to accept XBL-based form controls? | ||
** How do we guarantee a particular base binding will always apply? | ** How do we guarantee a particular base binding will always apply? display:none; breaks us in XBL 1. | ||
** Do we possibly want to replace current non-text inputs with [http://www.mozilla.org/xpapps/MachVPlan/xblforms.html the XBL Form Controls plan]? | ** Do we possibly want to replace current non-text inputs with [http://www.mozilla.org/xpapps/MachVPlan/xblforms.html the XBL Form Controls plan]? | ||
* Probably best to do layout and implementation as separate bindings. | * Probably best to do layout and implementation as separate bindings. | ||