InformAction Forums

Nice find! http://i.psyche.me/applaud.gif Thanks for reporting back. In my experience e10s in Firefox before 57 was quirky. I checked several times to determine that the lone setting that kept it from working was the browser.tabs.remote.force-enable;true Interesting. ...

... at least 5.1.7 if not older. These are the changes I'd made... https://fossbytes.com/how-to-make-firefox-faster-by-enabling-multi-process-e10s-manually/ Even pages that won't load on first try now, were loading back then after enabling multi-process, so I thought nothing of the change ...

... first post: "Last week, we released Firefox 77, which turned out to break all webpages sent using compression (like gzip) if you had disabled e10s using this environment variable." Kruitbosch then goes on to complain that unless the environment variable is done away with the world will ...

After some testing it seems to be related to noscript when e10s are disabled through the environment variable. I hope it gets taken a look at since so many of us are forced to disable multi-process as firefox runs so much better without it. If not, noscript ...

Any other minor details left out?
I'm still crash free (& never did quite follow the twitter end)?


(Disabling e10s does nothing to alleviate Sessions restore windows in random order. Sad.
But not to fear, we have Cortana - oh wait, that's Win10 - we have... Pocket .)

After some testing it seems to be related to noscript when e10s are disabled through the environment variable. I hope it gets taken a look at since so many of us are forced to disable multi-process as firefox runs so much better without it. If not, noscript ...

... right click and copy a link into another tab. It's also possible (will test tomorrow) that it's a bug with the the nightly, noscript and disabling e10s. To do that it's adding this environment variable: MOZ_FORCE_DISABLE_E10S - 1 It appears related to javascript since it only does it when noscript ...

It really looks we need synchronous messaging initiated from content (just like in the e10s API), as I advocated for years (since the Chrome extensions API was initially designed).

Some sites (well on one at least), I do get rules.
www.yahoo.com gives me Rules.
www.pcqanda.com does not.

Oops, I was confusing 52 & 56. So... FF 52.9 with NoScript 5.1.9 installed, is not showing Rules on my end? Regardless of the value of, browser.tabs.remote.autostart (& restarting). (Is that the correct Pref?) (I started with a new Profile, initially with SM 2.49, then the same with 2.53, th...

therube wrote: ↑Thu Jan 03, 2019 3:48 am (Was going to check FF 52, but I don't have my signing hack in there, so forgetaboutit! [said nicely].

What signing hack? I don't use any "hack" to disable requiring addon signing, I just set xpinstall.signatures.required to false and it's done.

OK, lets start again... Actual results: CSS rules pane is blank. The pertinent part. And for those who don't know what they're supposed to be looking for or what they're looking at... "My" (hacked version) Immaterial (to this issue). So... SeaMonkey 2.49.5 & Basilisk (FF 52 based, I be...

Assuming I've done it correctly "my" 5.1.9rc1 looks to be working correctly. SeaMonkey 2.49.5, 2.53, Basilisk 2018.12.18 (all x64, Windows 7 x64). "My" (hacked version), https://forums.informaction.com/viewtopic.php?f=10&t=23319. (IMO, some extension [internal] settings, feat...

... 5.1.9rc1, and I can still reproduce the issue there. So I tried Firefox 52.9, and could not reproduce this issue there...until I tried disabling e10s. UXP-based apps, e.g. Basilisk , are also affected. So is this a NoScript issue, or a platform issue?