Global:1.9 Trunk 1.8 Branch Plan: Difference between revisions

Global:1.9 Trunk 1.8 Branch Plan (view source)

2 bytes added , 18 December 2005

m

avoid extra redirect

Confirmed users, Bureaucrats and Sysops emeriti

722

edits

@@ Line 101: / Line 101: @@
 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=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.
+A: Fixing [https://bugzilla.mozilla.org/show_bug.cgi?id=210986 window targeting] to support better [https://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.