Auto-tools/Projects/Mozmill/Meeting-2011-09-20: Difference between revisions

 
(One intermediate revision by one other user not shown)
Line 8: Line 8:
** [https://bugzilla.mozilla.org/buglist.cgi?list_id=670918&resolution=---&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=mozmill-2.0%3F&component=Mozmill&product=Testing 2.0?]
** [https://bugzilla.mozilla.org/buglist.cgi?list_id=670918&resolution=---&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=mozmill-2.0%3F&component=Mozmill&product=Testing 2.0?]
** [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+]
** [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
* Fennec
** 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
canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,714

edits