Confirmed users
146
edits
DOM/Web Forms 2.0: Difference between revisions
→Possible Approaches
| Line 52: | Line 52: | ||
** 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]? | ||
** We must still inherit all the properties and methods on HTMLInputElement (including the ones defined in WF2)... how much of that should be on nsHTMLInputElement.cpp and how much in bindings? | ** We must still inherit all the properties and methods on HTMLInputElement (including the ones defined in WF2)... how much of that should be on nsHTMLInputElement.cpp and how much in bindings? | ||
* | * It would probably best to do layout and implementation as separate bindings. That way, the appearance could be flexible, while the DOM properties and methods would be a base binding that must always apply. | ||
=== C++ === | === C++ === | ||
| Line 65: | Line 65: | ||
Cons: | Cons: | ||
* More effort than it's worth? | * More effort than it's worth? | ||
== XTF == | |||
Smaug has proposed we could modify XTF to allow for XBL bindings on new HTML elements. If we could do the same for <html:input> types as well, this could be very helpful. | |||
Pros: | |||
* This could give us the advantages of XBL, without the disadvantage of someone disabling a needed binding. | |||
Cons: | |||
* Extra layers of redirection. | |||
== Technologies == | == Technologies == | ||