Currently there is no FF 48 for Power BE platforms.
However, there is a way of enabling a major feature of 48 while using 47 - multiprocesses whice improves FF for me on my non 3D or 2D enabled installation (Southern Islands card):
"browser.tabs.remote.force-enable" => add a new boolean to about:config and give it the setting "true".
* SLIGHT WARNING *
Some older extensions that haven't been updated might have issues with this setting.
Srtest wrote:Currently there is no FF 48 for Power BE platforms.
However, there is a way of enabling a major feature of 48 while using 47 - multiprocesses whice improves FF for me on my non 3D or 2D enabled installation (Southern Islands card):
"browser.tabs.remote.force-enable" => add a new boolean to about:config and give it the setting "true".
* SLIGHT WARNING *
Some older extensions that haven't been updated might have issues with this setting.
Hi Srtest,
Many thanks for the hint. I tested it on ubuntu MATE 16.10 today. It improves FF definitely. For example Facebook. It works faster. It also works with ViewTube.
The muiltiprocesses setting in its current state isn't for everyone it might even degrade your performance according to which addons/plugins you use. Hopefully that setting (officially named Electrolysis) would be better at newer releases.
You can check what works/enabled on your FF or what's not with "about:support".
Srtest wrote:The muiltiprocesses setting in its current state isn't for everyone it might even degrade your performance according to which addons/plugins you use. Hopefully that setting (officially named Electrolysis) would be better at newer releases.
You can check what works/enabled on your FF or what's not with "about:support".
I have it right now on my Ubuntu 16.10 LXQt and there is a major bug that collapses the browser, or, if you use the trick I provided which forces threaded tabs then only the "bad" tab collapses while the browser stays open. I think it might be something to do with java although I don't have the personal tools to asses it. Of course the issue of PowerBE as a cause of bugs is always there and the trouble in compiling it over the last few versions suggest that. Another direction could be me using SI and FF pushing reliance on hardware acceleration or an addon which relies on something like that (although it still behaves like that after disabling addons). Lastly, it doesn't happen on all of the pages.