user-overrides.js for Firefox update

I updated my user-overrides.js supplement for the 'ghacks' user.js for Firefox. You can grab the file here and the changes here. This version coincides with Firefox v78.

7 thoughts on “user-overrides.js for Firefox update”

  1. Hello,
    How can I safely apply the changes in this version of your user-overrides.js as I currently use the previous one in which I change a few things? Should I just take the new one, then paste the lines from the previous one (only the lines between * YOUR CUSTOM CODE GOES BELOW THIS LINE and * YOUR CUSTOM CODE GOES ABOVE THIS LINE)?
    Thank you.

    1. > Should I just take the new one, then paste the lines from the previous one (only the lines between * YOUR CUSTOM CODE GOES BELOW THIS LINE and * YOUR CUSTOM CODE GOES ABOVE THIS LINE)?

      yes – and don’t forget to do the 2 checks afterwards when you start Firefox

      1. About the diffs. I ran the updater with the -c switch and it generated a diff file:
        — userjs_diffs/past_userjs.txt 2020-07-04 12:24:30.586101386 +0200
        +++ userjs_diffs/current_userjs.txt 2020-07-04 12:24:30.590101245 +0200
        @@ -132,2 +132,10 @@
        -user_pref(“_user.js.parrot”, “2200 syntax error: the parrot’s ‘istory!”);
        -user_pref(“dom.disable_window_move_resize”, true);
        +user_pref(“media.autoplay.blocking_policy”, 2);
        +user_pref(“dom.disable_window_open_feature.close”, true);
        +user_pref(“dom.disable_window_open_feature.location”, true);
        +user_pref(“dom.disable_window_open_feature.menubar”, true);
        +user_pref(“dom.disable_window_open_feature.minimizable”, true);
        +user_pref(“dom.disable_window_open_feature.personalbar”, true);
        +user_pref(“dom.disable_window_open_feature.resizable”, true);
        +user_pref(“dom.disable_window_open_feature.status”, true);
        +user_pref(“dom.disable_window_open_feature.titlebar”, true);
        +user_pref(“dom.disable_window_open_feature.toolbar”, true);

        I am a little confused here, do I have (in the user-overrides.js) to delete the lines which begin wit the “-” sign (in the diff…txt file) and add the lines which begin with the “+” sign?

        1. no – the lines beginning with (-) are prefs that were removed from user.js either by the ‘ghacks’ user.js project or prefs you removed from user-overrides.js (user-overrides.js is appended to user.js, so when you run the updater script it’s seeing the content from user-overrides.js also)

          and the (+) lines are prefs that were added, again, either by the ‘ghacks’ project or by you in user-overrides.js

          in this case, all of these prefs were added/removed by the ‘ghacks’ project so there’s nothing you need to do unless you wanted to change the value one of the prefs in which case you would copy it to the appropriate section of user-overrides and change the value there

          1. Ok, so this is done automatically? I was confused because I read:
            “Over time it is possible that your user-overrides.js file will contain preferences that are obsolete. The ‘ghacks’ user.js file contains a list of some of these preferences in the section titled [SECTION 9999]: DEPRECATED / REMOVED / LEGACY / RENAMED and these preferences should be removed from your user-overrides.js file. One very tedious way to do this is to go through the list line by line and see if they are duplicated in your user-overrides.js. An easier way is to use the -c switch (documentation here) when you run the updater script which will output a ‘diff’ file containing the differences between the old user.js and the new one.”

            “and these preferences should be removed from your user-overrides.js file”

            So when I run he updater.sh with the -c switch it outputs the diff…txt file, but I have nothing to do, the diff…txt file is just for information purpose?

            1. > So when I run he updater.sh with the -c switch it outputs the diff…txt file, but I have nothing to do …

              not necessarily – assume for example the pref "this.something", true; exists in the user.js and you want to set it to ‘false’, so you copy it to user-overrides and change the value

              then later the value is changed to ‘false’ in user.js, or it is moved to the depreciated section – in this case it should be removed from user-overrides (and the prefsCleaner script needs to be run also)

              i take care of the existing prefs included in user-overrides, so you don’t have to worry about those, but any custom prefs that you add should be checked to see if they are duplicated in user.js when ever user.js is updated

              if you only have a few custom prefs, you can search for them in user.js one-by-one, but if you have many you can use a regular expression if you know how – i can give an example if you like

Leave a Reply

Your email address will not be published. Required fields are marked *