we still have the argument, but it does nothing. it should set browser.tabs.remote.autostart to true as that turns e10s for all windows. similarly, add an internal "e10s" flag to package.json to enable running only specific test addons in e10s mode for the transitional period.

except, cfx is on life support, so I hope it isn't a lot of work. This should be targeted at the jpm / aom project as well.

(In reply to Jeff Griffiths (:canuckistani) from comment #1) > except, cfx is on life support, so I hope it isn't a lot of work. this is nothing big (except for unrelated hair pulling in bug 1006043), and is absolutely necessary. > This should be targeted at the jpm / aom project as well. not really related to native/AOM stuff, and to JPM only if/when we start running tests with it, and only if that happens before e10s is "done".. ;)

Commits pushed to master at https://github.com/mozilla/addon-sdk https://github.com/mozilla/addon-sdk/commit/5c6c59e4917c5d61ff433886853ea20d0fb1819d bug 1004833 - enable e10s argument and flag plus a new e10s test addon https://github.com/mozilla/addon-sdk/commit/46171025eb797bd04d51b47fe3ae117bb599de55 Merge pull request #1484 from zombie/e10s-cfx-flag bug 1004833 - enable e10s argument and flag, r=@gozala