MozillaZine

Web Hypertext Application Technology Working Group Launches Mailing List

Friday June 4th, 2004

Ian Hickson writes: "Some of you may be interested to hear that people from Opera and Mozilla have set up an open mailing list for discussing Web Forms 2 and other new specs that have been discussed in various places over the last few months."

The list is the public forum of the newly-formed Web Hypertext Application Technology Working Group, an organisation made of contributors from several major Web browser development teams. Current invited members are Brendan Eich, David Baron, David Hyatt, Håkon Wium Lie, Ian Hickson, Johnny Stenback and Maciej Stachowiak.

The group is working on specifications for Web Forms 2.0, Web Apps 1.0, Web Controls 1.0 and a CSS object rendering model. This work will be largely done outside of the World Wide Web Consortium, though finalised versions of the specs are expected to be submitted for formal standardisation. While the decision to operate independently of the W3C may be seen as controversial, many feel that formal standards bodies move too slowly to react to proprietary technologies such as Microsoft's forthcoming XAML. In addition, many in the W3C are pushing for Web applications standards based on technologies such as XForms and Scalable Vector Graphics, whereas the members of the WHATWG favour backwards-compatible HTML-based solutions, which they believe would be easier to implement and more likely to be adopted by Web developers.


#20 When will they ever learn?

by pete27

Sunday June 6th, 2004 12:22 AM

You are replying to this message

I can't understand why nobody adopts MS technologies, even when they don't comly with standards. Fact is that MS owns >90% of the browser market. So <10% care about mozilla- opera task groups. The average user has IE6 and is happy with it as long as he can browse the web. Competing products like Mozilla will only have a chance to grow significantly when they are backward compatible with IE. So other browsers have to adopt IE completely and then implement features on top of it. In a few years every browser will have to deal with XAML. Not because it's a W3C or because it's cool, but simply because 90% of the market uses it.