Mobile/e10s/Frontend

Note: When you make bugs for these tasks, please mark them blocking bug 516521

Worklist for refactoring the mobile-e10s front-end code before merging into mobile-browser.

• openURLInFrame can be merged now as it won't cause any problems for mobile-browser.
• Merge the KeyEvent handling into the current Clicker object.
• Remove/refactor contentWindow and contentDocument mock objects from the remote browser XBL.
• Add "isRootWindow" concept to aWebProgress argument of the progress listener interface methods (e10s and non-e10s).
• bug 566586 Remove MessagePasser helper code.
• Remove the try/catch wrap from the nsIAlertService code in browser.js
• Create a message API for "DOMTitleChanged", "DOMLinkAdded" (or just "DOMSearchEngine") and "DOMWindowClose". Use the API for e10s and non-e10s.
• Create a scroll message API for scrollTo and scrollBy. For example, browser.messageManager.sendMessage("Content:ScrollTo", {x: someX, y: someY });
• Move mIconURL support into the browser XBL binding (e10s and non-e10s).
• bug 566500 (mbrubeck) - Move viewport metadata support into the browser XBL binding (e10s and non-e10s).
• Move identity support into the browser XBL binding (e10s and non-e10s).
• Tab progress listener cleanup (_listener, removeProgressListener, etc).

FormHelper (vivien)

I have tried a rewrite of the FormHelper code starting from mobile-browser instead of e10s and I have finished pretty close to what stechz has did. The two changes I would like to see are:

• Rename some methods of the e10s code to be closer to the actual mobile-browser's code
• Move as much as possible the FormHelper's code to its own file

OfflineApps

A quick test show that offline apps are not working (but it can be a user error on my side)

• MFinkle thinks DougT thinks this should be working now bug 552829. But it really does work, so you can ignore this section.