GetPrefBranch() – Gets the root of the preferences tree. With all credit to the SIPB Firefox Locker, those functions are: The file prefcalls.js defines a set of convenience functions that are provided for autoconfig authors. That pref line above is not the same as a pref line in a preferences file, it is a call to a function called pref().
Firefox esr 17.0 full#
(The 1st is that the first line in the autoconfig file is ignored.)Īutoconfig files are real Javascript files that allow full code execution including access to XPCOM components. This is the 2nd most misunderstood thing about autoconfig files. Now after reading the first article in this series, you might be thinking “Oh, the format is exactly the same as a default preferences” and you would be very, very wrong. IMPORTANT: Start your code on the 2nd line So now that you’ve told Firefox where to get the file and whether or not to obfuscate the file, it’s time to create it. There’s a bug open to have Firefox not obscure the file. Most people turn off the obfuscation by setting this preference in the same file where you specified the config file: (Thunderbird has removed the need to shift the bytes – the autoconfig can be used as is.) If you would like to obfuscate your config file by byte shifting it, you can do that. Remember that byte shifting we talked about? With Firefox it is a shift by 13 bytes and it is still required by default. You can specify any name you like, but the file still must be located in the same place as the executable. In order to use a config file, you have to specify that you want to use one in a default preferences file. First off, a config file is not required. Fortunately for us, the autoconfig infrastructure was left in place.Īutoconfig files are handled a little differently in Firefox then they were in Netscape Communicator. It was written using a lot of technology that made it difficult to port to something usable. When Netscape was open sourced, MCD fell by the way side. The file was byte shifted by 7 bytes, so a user could not modify the file, and if they removed it, Communicator wouldn’t start at all. MCD worked by generating a new netscape.cfg with various customizations and then packaging that file as a part of a standard Communicator install. If you were to look at an installation of Communicator, you would see a file called netscape.cfg file in the same directory where the executable was located. MCD was Netscape’s enterprise solution for customizing Netscape Communicator. This is the story of Netscape Mission Control Desktop (MCD).
Firefox esr 17.0 series#
Next up in our series on customizing Firefox is the infamous autoconfig file.īefore I go into detail about how autoconfig works, I want to give you a quick history lesson. I’m doing a series where I go over each method of customizing Firefox (that I know about) and detail how it works and what it can change.
0 kommentar(er)
