= About This Roadmap And Branches/Releases =
This roadmap describes the technology capabilities of the Mozilla platform, often known as "Gecko", in the 1.9 release. The current plan of record -- product delivery vehicle for this being the record -- has that 1.9 technology being part of a Firefox 3 release scheduled for will be explored, discussed, and refined in another roadmap process, to which this document will link in the first quarter of 2007very near future.
This The work described in this document will be performed -- in several cases is already <i>being</i> performed -- on the trunk of Mozilla CVS, with the 1.8 branch preserved largely intact during the development of Firefox 2. Some of the features listed below may be pulled forward into that 1.8 branch if needed for consumption by Firefox 2product releases off that branch, and they are indicated by (graphic to be named later)but you shouldn't count on it.
= Major Areas Of Development =
The XBL work is largely drawn from Ian Hickson's and David Hyatt's work on sXBL and XBL2. Further investigation is required to determine how much of the XBL2 draft will be necessary or implementable in the 1.9 timeframe, but some pieces such as an improved attachment model, clearer lifecycle semantics, and language neutrality are prerequisites for desired application or 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. Improvements to the XUL box model, based on the specification work done, again, by Hickson 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 the W3C, WHATWG, or other appropriate venue. (In fact, most of the gain sought by a "shining XUL2 jewel" plan will likely be delivered by these box-model improvements and cross-content rationalization, rendering the former not only a non-goal but also a non-issue.)
== Web app deployment and capability improvements ==
== Embedding and application deployment ==
For many application developers, putting Mozilla technology inside or underneath their applications has been a bittersweet experience. While they are rightly excited to have the power of the Mozilla platform at their disposal, the state of our embedding interfaces and application-launch facilities have created significant impediments to their productivity, and introduced expensive fragility into their environments. While we wish to see the plight of these developers improve, we do not believe that the "second-class" nature of 3rd party applications can be entirely wiped from our world.
Instead, we will seek to make our own applications use the same...
=== XULRunner ===