I want to reiterate that Mozilla drivers are in favor of an XForms implementation being developed, so long as it doesn't duplicate a bunch of existing code (e.g., so long as it doesn't jam all of Xerces in, or try to change XML parsers without buying off on all the unautomated regression testing that would entail).
A plurality of drivers are in favor of including XForms support by default if the overhead is small enough (~30K code footprint, no startup or page-load performance hit for XForms-less pages, was my straw man).
I thought I would mention one problem that Elliotte does not mention in his blog, especially when he asserts:
I think what he misses is that XForms is a compelling enough story to displace IE.
Even if enterprises and governments using IE currently want XForms, they may rather use formsplayer than switch to Mozilla, because they also have dependencies on Active X, IE DOM quirks, and other IE proprietary features. We at Mozilla Foundation, and at Netscape/AOL before that, have run into such migration hurdles too often to count.
Still, if you know of organizations that would likely switch from IE to Mozilla if only Mozilla had native XForms support, please let me know of them, or at least of their requirements, if you can.
/be _______________________________________________ mozilla-layout mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-layout
