Am 08.08.2017 um 09:54 schrieb Per Jessen:
Wolfgang Rosenauer wrote:
Am 08.08.2017 um 09:39 schrieb Per Jessen:
Wolfgang Rosenauer wrote:
Am 08.08.2017 um 09:33 schrieb Per Jessen:
I'm going to open the ticket again - it seems quite clear that the issue is with openSUSE, not with Firefox.
No, my results are exactly the same for openSUSE Firefox 55.0b13 and upstream Firefox 54.0.1. This is not openSUSE specific as far as I can tell.
Okay - how come it works for some people and not for others then? I can't make sense of that.
Behaviour is different if e10s/content process separation is active or not.
Check with about:support the "windows with multiple content processes" or something similar ("Fenster mit mehreren Prozessen").
I see "Multiprocess Windows" = 1/1 (Enabled by default). Are you saying it will work if I change this? (not sure how).
Under Extensions, I see "Multi-process staged roll-out, version 1.10, enabled=true.
try setting browser.tabs.remote.autostart and browser.tabs.remote.autostart.2 to false I think this still disables e10s. And try again. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org