Global:1.9 Trunk 1.8 Branch Plan: Difference between revisions

Global:1.9 Trunk 1.8 Branch Plan (view source)

227 bytes added , 13 December 2005

Confirmed users, Bureaucrats and Sysops emeriti

419

edits

@@ Line 90: / Line 90: @@
 Q: What's an example of API or bug-compatibility skew where #ifdefs might be required in front-end sources?
-A: Fixing [http://bugzilla.mozilla.org/show_bug.cgi?id=|XXX] to support better tabbed browsing is one example.  A hack-fix only for Firefox could be made to the 1.8 branch, to minimize risk.  Meanwhile, to avoid duplication of effort and excess bug habitat, we would like to fix window targeting on the trunk by unifying embedding and XUL-app APIs and implementation, which probably means incompatible API changes.
+A: Fixing [http://bugzilla.mozilla.org/show_bug.cgi?id=210986|window targeting] to support better [http://bugzilla.mozilla.org/show_bug.cgi?id=308396|tabbed browsing] is one example.  A hack-fix only for Firefox could be made to the 1.8 branch, to minimize risk.  Meanwhile, to avoid duplication of effort and excess bug habitat, we would like to fix window targeting on the trunk by unifying embedding and XUL-app APIs and implementation, which probably means incompatible API changes.
+Another example: XUL box layout standardization may break compatibility at a few edge cases, requiring #ifdefs in toolkit or other front-end XUL sources.
 Q: What about the Firefox 2 work already under way on the trunk?