1552442 - Work out what to do with e10s force-enable check in mobile/android

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: Testing, task, P3)

Description

[:Gijs (he/him)]

Just switching it to check browser.tabs.remote.autostart makes robocop tests unhappy (presumably because they get the default mochitest user.js set of files, and one of those turns on e10s, but I haven't verified this).

Comment 1

[:Gijs (he/him)]

As noted on bug 1549855, I'm not sure how much point there is digging into this bug given the robocop issues, so I probably won't prioritize fixing it myself unless I'm missing something about the impact.

Comment 2

[KOLANICH]

I vote for allowing it being disabled. When enabled the performance is awful.

Comment 3

[:Gijs (he/him)]

(In reply to KOLANICH from comment #2)

I vote for allowing it being disabled. When enabled the performance is awful.

This bug is about fennec (Firefox for Android). It defaults to e10s off, and this bug is about the details of which pref governs forcing it on.

Comment 4

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.