+- PINE64 (https://forum.pine64.org)
+-- Forum: Pinebook (https://forum.pine64.org/forumdisplay.php?fid=76)
+--- Forum: General Discussion on Pinebook (https://forum.pine64.org/forumdisplay.php?fid=77)
+--- Thread: Update to Firefox 55.0.X (/showthread.php?tid=4981)
Update to Firefox 55.0.X - Luke - 08-21-2017
For those of you who haven't done so already, do update to Firefox 55.0.2 (at the time of writing). Its a tangible improvement over the previous iteration in terms of performance on the Pinebook. Also, don't forget to apply these tweaks.
RE: Update to Firefox 55.0.X - Wizzard - 08-21-2017
It is a little faster, but still slower than Chromium. Also, I was not able to find some options like
network.http.pipelining true
Network.http.proxy.pipelining true
network.http.pipelining.maxrequests 8
RE: Update to Firefox 55.0.X - Luke - 08-21-2017
(08-21-2017, 06:53 AM)Wizzard Wrote: It is a little faster, but still slower than Chromium. Also, I was not able to find some options like
network.http.pipelining true
Network.http.proxy.pipelining true
network.http.pipelining.maxrequests 8
I find Chormium slower - especially post Firefox 55. Also, for some reason chromium uses so much RAM during normal operation that my PBs end up using swap.
RE: Update to Firefox 55.0.X - Wizzard - 08-21-2017
I tried to use Firefox a few days ago when the 55 version was released and it did not convince me. Maybe I will try that firefox settings again.
RE: Update to Firefox 55.0.X - robbiemacg - 08-23-2017
Interesting change: since the update .java source files are no longer opening in browser for me (open/save dialogue pops up). I'm heading to FF support forms to see if I can figure out what got flipped now, but if anyone has a sense of what settings I need to change, I'd be grateful for some advice.
RE: Update to Firefox 55.0.X - robbiemacg - 08-24-2017
For now, I think I've verified experimentally that that new release is trying to do something to sanitize data/files that my previous release was not. Those files which were failing to display all began with a wildcard import statement (something like, import java.util.*
. Adding a comment at the beginning of the file results in a change in browser behaviour, and files are displayed as text once again... So, the plot thickens.