- From: Anne van Kesteren <fora@annevankesteren.nl>
- Date: Wed, 16 Mar 2005 19:41:25 +0100
- To: John Boyer <JBoyer@PureEdge.com>
- CC: "Goodrich, Christopher Michael" <cmgoodr@sandia.gov>, www-forms@w3.org
John Boyer wrote: > This is curious to me. If not with a pile of javascript, then can you > explain how else the new attributes and their values will be given > meaning other than by a browser upgrade? I thought we were comparing "native implementations". If you want to implement WF2 in a curernt browser, then yes, you need scripting. However, you could create a plugin as well, as is done for XForms. > Without scripting, isn't it the case that the WHAT-WG is no more > compatible with IE and other existing browsers than XForms? Not really. Where IE would download a page using XForms embedded in XHTML it would show a page using WF2 in HTML. Also, the form can still be submitted, but client-side validation is lost. > With scripting, isn't it true that existing browsers can be used for > the WHAT-WG proposal? But isn't it also true that with scripting the > existing browsers can be used to support XForms? The first is true. The second is false. IE doesn't support the 'application/xhtml+xml' namespace, for example. -- Anne van Kesteren <http://annevankesteren.nl/>
Received on Wednesday, 16 March 2005 18:41:50 UTC