This bug is a reminder to remove the UI testing features and unlocalized strings before we enable e10s by default.

I think we should remove the "Open e10s Window" menu item sooner than planned. The "browser.tabs.remote.autostart" pref enables the add-on compatibility shims, but the menu item does not. As I predicted, this is causing user confusion and we are getting false positive bug reports for add-ons that work when the shims are enabled (e.g. bug 930787 comment 13).

Move old M2's low-priority bugs to M6 milestone.

Re-nomming this, seems like we probably want to keep this on on aurora but turn off before beta which would mean this should be in m7 or m8

Will you be removing the ability to use non-e10s windows? When I have a problem in Nightly one thing I often do is try to reproduce in a non-e10s window. I think it will be useful for advanced users when troubleshooting. Can you make it hidden, example if shift key is down we'll still see 'New Non-e10s Window' or do something where it is still accessible even though hidden by default?

Removing from m8 as we put this under bug 1204030

Unassigning bugs I'm not currently working on. I can take it back when it comes time to work on this.

[Tracking Requested - why for this release]: e10s rollout to beta 45 targeting users without addons

I agree with this request. Very occasionally I do have to check out a non-e10s window, because it is not entirely compatible. With the ability to open up a non-e10s window,I could see more quickly if the problem was caused by e10s or not. It would also make it more likely that I would keep testing e10s on beta. (In reply to Ray Satiro from comment #4) > Will you be removing the ability to use non-e10s windows? When I have a > problem in Nightly one thing I often do is try to reproduce in a non-e10s > window. I think it will be useful for advanced users when troubleshooting. > Can you make it hidden, example if shift key is down we'll still see 'New > Non-e10s Window' or do something where it is still accessible even though > hidden by default?

[Tracking Requested - why for this release]: e10s won't ship with 45. Updating the title: l10n don't like when we remove strings. It adds some unnecessary tasks.

Tracking so we don't forget to switch this if e10s goes to release in 46.

This is duplicated to a meta bug that doesn't seem to link to a similar bug. Is it something that we know is fixed elsewhere?

covered by bug 1004533 and bug 1161260, nothing to do here