Upcoming Firefox 57 ("Quantum") is twice as fast as Firefox 52

ok looks like many people have the issues, and useless replies from paypal (+accusations paypal making vivaldi persona non grata)
eg. https://www.paypal-community.com/t5...18-deadline-for-updating-browser/td-p/1516117
but seems they require >= tls 1.2 authorisation which is available in ff since 49
https://esellercafe.com/paypal-merchants-have-until-june-30-to-upgrade-to-tls-1-2/
can check what your system has via https://www.ssllabs.com/ssltest/viewMyClient.html
from https://support.mozilla.org/en-US/questions/1198543
am trying an about:config fix.

just update?

Was just posting something in another thread that reminded me of this - I would urge updating to a newer version than 49 due to the Ogg Vorbis remote code execution flaw unless you are 110% sure you are only browsing probably safe sites like your bank, etc. even then if there was say an attack on an ad provider you might be vulnerable. There were a couple of pretty serious remote code execution issues resolved as well as Meltdown/Spectre mitigations in FF 59+ which you really want to have.

End of the day though its your OS, etc. *shrugs*
 
According to this all the browsers are losing out to Chrome which sits at 62.8%.

You would think with all this privacy backlash which has been going on recently people would wise up and avoid it and go with alternatives but apparently not.

If people cared enough about privacy android would have died, they simply dont.
 
Testing a new theory on graphical corruption , for which I still think youtube may contribute.
My older gpu does not support VP9 codec acceleration (I see 6450 did not either) which is default on youtube, so instead it will decode in s/w.
So I am trying a h264ify add-on in FF.

not sure if (other than looking for gpu activity) you can confirm how vidoes are decoded in ff ???
 
Switched over to Privacy Possum from Privacy Badger to test how that performs, it's made by one of the guys who worked for EFF but left due to the direction they were going with blocking on Privacy Badger.
 
Switched over to Privacy Possum from Privacy Badger to test how that performs, it's made by one of the guys who worked for EFF but left due to the direction they were going with blocking on Privacy Badger.

Any other useful extensions for an FF noob? Only just started using it over Chrome.
 
Any other useful extensions for an FF noob? Only just started using it over Chrome.
All you need:

Extensions:
- uBlock Origins (ad blocker, also works on android)
- DuckDuckGo Privacy Essentials (tracker blocking on pc, https everywhere, privacy ratings)

Settings
- Tracking Protections ON (tracker blocking on android)
- Disable all search engines except DuckDuckGo

Advanced Settings:
- First Party Isolation ON https://www.ghacks.net/2017/11/22/how-to-enable-first-party-isolation-in-firefox/

Web Search
- Use https://start.duckduckgo.com instead of Google
 
Any other useful extensions for an FF noob? Only just started using it over Chrome.

I currently use DDG for my search engine and these addons:

Bitwarden,
Ublock Origin,
HTTPS Everywhere,
Privacy Possum,
Decentraleyes,
Flagfox,
Facebook container,
Reddit Enhancement Suite,
Ark dark Theme.
 
All you need:
....
Advanced Settings:
- First Party Isolation ON https://www.ghacks.net/2017/11/22/how-to-enable-first-party-isolation-in-firefox/

... instead of Google

with the first party isolation have you had any problems with either having to do CAPTCHA's or, additional cookie consent requests.?
I see these are listed as potential issues with FPI, and,
even with noscript I have many problems of that type , but put up with it , a necessary evil.
With youtube too, with noscript (using abe) I have to let it access google for cookies otherwise it always request google consent.

Sometimes, access to websites when using noscript can be slow and I have wondered if the web-sites intentionally make you wait, if they do not manage to access cookies or advertising web-sites they expect to see . ie 'they' are taking counter-measures.
 
Has anyone experienced what appears to be screen tearing when scrolling in FF? I've tried reloading FF, rebooting PC, disable hardware acceleration but the tearing remains.
 
Has anyone experienced what appears to be screen tearing when scrolling in FF? I've tried reloading FF, rebooting PC, disable hardware acceleration but the tearing remains.
maybe disable smooth scrolling ? otherwise the next renderer is meant to do 60fps
you're not running monitor at a high fps ? since i guess that exacerbates issue where image has not been fully drawn in video memory before refresh.
 
Back
Top Bottom