Latest revision as of 22:58, 20 September 2011

QA Section

Content window handler class has been landed (with ui map support included)
Support for Fennec is raising in priority more and more. We need a good strategy on it.

@@ Line 9: / Line 9: @@
 ** [https://bugzilla.mozilla.org/buglist.cgi?list_id=670927&resolution=---&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=mozmill-2.0%2B&component=Mozmill&component=Mozmill%20Utilities&product=Testing 2.0+]
+* Mozmill
-* Isolating Mozmill's driver
+* Fennec
-** [https://github.com/ahal/mozmill/commit/eb02a3311c0f3e10abc3af5d6f409cd93b10fa68 diff]
+** e10s has to be supported first before we can do anything for Fennec
+*** messaging between content and chrome
+*** content can call chrome only asynchronously
+*** chrome can call content synchronously/asynchronously
+*** a single content process on fennec - multiple processes on firefox
+*** we cannot use the global browser object
+** jsbridge works with e10n turned on
+** we have to get rid of the gBrowser object
+** Andrew is working in a separate responsiveness harness which makes mozmill driver ready for e10s
+*** Isolating Mozmill's driver
+**** [https://github.com/ahal/mozmill/commit/eb02a3311c0f3e10abc3af5d6f409cd93b10fa68 diff]
+* timeline
+** mozmill e10s support by q4 2011