Updating firefox 56 whitout getting quantum?
I am currently using Firefox 56 and its starting pestering me about being criticaly outdated, so I am would ask if theres any way to update my FF whit out getting quantum in as I find it about as flawed as microsoft internet Explorer 6, so basicaly can keep v56 as it is but updated?
All Replies (6)
Hi !
Updating Firefox version 56 means updating to Firefox 57 (aka : Quantum), which you should definately do (I will spare you the lecture as to why).
But would you please tell us what your problems are with Firefox 57 ? We just might be able to get those problems out of the way.
Worth a try .......
Ok some of my issues/problems whit FF 57 is:
1. When I open up a new empthy page in FF 56 I get 15 pinned pages to pick from where 57 gives less, frankly I would like more than 15 but getting less is a minor annoyence as part of my work I use them.
2. Ui/hud, I strongly prefere the rounded curves of 56 over the square "photon" style 57 is using.
3. 57 is slowing down my pc when I got serval photoshop works going on when I am making a video, 56 do not.
4. 57 sometimes never finish loading windowes(little round arrow keeps spinning).
5. 57s button lay out, I have grown costume to where all the buttons and tools are located on/in 56 and I like it that way.
6. Some of my add-ons dont work whit 57.
7. 57 just feel alot slower than 56.
These was what I could think off atm, however number 1 and 2 are my main reason fore sticking to 56 atm.
KjeldPedersen said
Ok some of my issues/problems whit FF 57 is: 1. When I open up a new empthy page in FF 56 I get 15 pinned pages to pick from where 57 gives less, frankly I would like more than 15 but getting less is a minor annoyence as part of my work I use them.
This should take care of your number one problem (fingers crossed) :
Type in the address bar about:config (press Enter) (promise to be careful, if asked)
Type in the search bar and look for the preference :
browser.newtabpage.activity-stream.topSitesCount"'
and change its value to 18 (if you want 3 rows)
A value of 24 will give you 4 rows, 30 will give you 5 rows etc.
After you've changed the value, close and restart Firefox, in order for the change to take effect.
2. Ui/hud, I strongly prefere the rounded curves of 56 over the square "photon" style 57 is using.
Would you please take a look at this :
https://github.com/wilfredwee/photon-australis
Any good ?
I'm going to leave your nrs. 3 to 7 for somebody else (they just might no longer be an issue in Firefox 58, which was released yesterday .....)
As nobody else has come to your rescue yet, I will try to address the other problems.
Number 3 on your list (see also number 7) : Would you please take a look at the article Quick fixes if your Firefox slows down
Number 4 on your list : Websites show a spinning wheel and never finish loading
Number 5 on your list : Maybe you'd like to be a bit more specific as to which buttons you are talking about ..... (?)
Number 6 on your list : These are probably add-ons that haven't been updated and/or migrated to Webextension by their developers (they've had ample time to do so). Have you tried to contact these developers about it ?
Number 7 on your list (see also number 3) :
You could disable multi-process (e10s) and see if that'll make a difference.
Type in the address bar about:config (press Enter) (promise to be careful, of asked - well, you know the drill by now)
Type in the search bar and look for the preferences:
browser.tabs.remote.autostart and set it's value to false (default)
browser.tabs.remote.autostart.2 and set it's value to false
Then close and restart Firefox in order for the change to take effect.
Another thing to try on the 'about:config' page :
accessibility.force_disabled
and set its value to 1 (if it isn't already)
'Sure hope this helps .......
Ok so fare nr. 1 and 2 seams fixed many thanks for that. I shall test the rest in a day or two.
KjeldPedersen said
Ok so fare nr. 1 and 2 seams fixed many thanks for that. I shall test the rest in a day or two.
I'm glad that numbers 1 and 2 are no longer a problem !
As for testing the rest : take all the time you need !