updating Firefox version and migrating the config file.
When I upgrade Firefox versions, I create a new profile folder to test the newer version. When I upgraded to V101, I found Google Maps worked very well using the standard config file the install created, especially in relation to panning in Street View. then when I miggrated over my old config file from V88 Google Maps became very sluggish on panning. Clearly some config entries need tweaking. How do I know which class of config entries are used by Google Maps? I dont want to compare every single line of the config files..
Its about time Firefox came with a flyout when you hover over each config entry to tell us what it does?
All Replies (6)
It may not be the same issue but this is a similar thread.
Maybe check APZ prefs.
Is that a config file (?user.js) you created yourself or did you find those directions on internet ?
The user.js file is read each time Firefox is started and initializes preferences to the value specified in this file, so preferences set via user.js can only be changed temporarily for the current session.
Terry said
It may not be the same issue but this is a similar thread. https://support.mozilla.org/en-US/questions/1382871
Thats a separate issue re freezing/hanging. My question is related to panning speed , which changes due to differences in the config file prefs.js, and not any extensions being run.
cor-el said
Maybe check APZ prefs. Is that a config file (?user.js) you created yourself or did you find those directions on internet ? The user.js file is read each time Firefox is started and initializes preferences to the value specified in this file, so preferences set via user.js can only be changed temporarily for the current session.
No its about the main config file prefs.js I dont have a user.js file on my system, or any file named *APZ*.*
If no solution comes up then I suppose getting all the modified properties from my old V88 prefs.js file and manually adding them to the newer V101 prefs.js file is the answer, but what a laborious task.
Its upgrade problems like this, and the constant stylesheet changes that affect the user interface, that makes you avoid Firefox upgrades as long as you can, or think about using another browser. Just too much re configuration that has to be done with each upgrade.
Modified by drivvel
The 'apz' I mentioned above is not about a file, but about apz.* prefs (APZ = Async Pan/Zoom) that you can find on the about:config page and that can be present in prefs.js when there are prefs that do not have the default value.
Modified by cor-el
cor-el said
The 'apz' I mentioned above is not about a file, but about apz.* prefs (APZ = Async Pan/Zoom) that you can find on the about:config page and that can be present in prefs.js when there are prefs that do not have the default value.
OK I see those apz* configs, sounds like they are to do with touch screeens for mobile devices though? I will look at those first, but it seems the only way to solve this problem is to manually compare the old config with the new config each upgrade., which is going to take an hour or more. I have hunfreds of modified prefs.
This is why I dont upgrade until something breaks. I lasted on V88 for a year or so until I had to upgrade to 101.