Confirm, emeritus
419
edits
Changes
→XUL' and XBL2
The XUL and XBL languages have served Mozilla development very well, and are often taken as a model for XML-based UI development in other circles. In some cases, however, our implementations or their old specifications are incomplete, inconsistent, insufficiently robust, or not amenable to some important use cases (including remote XUL applications or rich mixing with other content types such as HTML or SVG). We seek to address these limitations, and generally improve the XUL and XBL development experience, with work in Gecko 1.9.
The XBL work is based on an existing design by Ian Hickson and David Hyatt, currently being developed in the mozilla-xbl list. Pending the complete specification, we can't be sure that all of XBL2 will be implemented in the 1.9 timeframe, but we are committed to at least an improved attachment model, clearer lifecycle semantics, and scripting language neutrality. These are prerequisites for desired 1.9-era application and platform features.
XUL work in Gecko 1.9 will not undertake to create a shining XUL2 jewel, but will instead work to preserve compatibility with "XUL1" where practical, and make clean breaks where unavoidable. Hence the tentative name XUL' (XUL Prime). Improvements to the XUL box model, based on the specification work done, again, started by Hickson Hixie and Hyatt , should provide a more consistent and flexible layout model for XUL developers, and help to rationalize XUL's interactions with other content types. This box-model work has been proposed for standardization, and Mozilla may participate in that at via the W3C, WHATWG, or other appropriate venueCSS working group. (In fact, most Much of the gain sought by a in any "shining XUL2 jewel" plan will would likely be delivered by these box-model fixed, improvements , and cross-content rationalization, rendering the former not only a non-goal but also a non-issue.)
== Web app deployment and capability improvements ==
