Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any reason why profile autoconfig is not used? #5

Open
philberthfz opened this issue May 9, 2023 · 0 comments
Open

Any reason why profile autoconfig is not used? #5

philberthfz opened this issue May 9, 2023 · 0 comments

Comments

@philberthfz
Copy link

philberthfz commented May 9, 2023

Rather than having users manually open about:config to change preferences, you can, in fact, include the preferences near the top of config.js

If I knew how to use git or do pull requests, I'd have done one. However, I don't. So instead, I'll simply recommend making the following changes to the config.js that you instruct users to put in the Firefox root folder. Simply add these lines below the //first line and above the try{}

pref("toolkit.legacyUserProfileCustomizations.stylesheets",true);
pref("svg.context-properties.content.enabled",true);
pref("ui.prefersReducedMotion",1);
pref("browser.display.windows.non_native_menus",0); 

These will automatically set the same preferences that the end user would set manually, and it automatically sets these preferences every time the browser restarts.

Optionally, you can also pre-configure other sensible default options using defaultPref instead of pref, which will only change an option if it hasn't been set or if the user resets their preferences to default. This is less obtrusive as if a user decides they really actually did want their tabs in the title bar or their UI density to be touch, they can set those options and the configuration script will not override them. As an example, the following four items pre-configure the settings I typically set when I enable this theme, which greatly speeds up installation whenever I need to set up a new profile:

defaultPref("browser.tabs.inTitlebar",0);	// Tabs seperate from title bar
defaultPref("browser.tabs.firefox-view",false);	// Disable firefox view button
defaultPref("browser.uidensity",1);		// Compact mode. 1=Compact, 0=default, 2= touch
defaultPref("browser.toolbars.bookmarks.visibility","always"); //Bookmarks bar always visible. Options are "always" "never" and "newtab"

Doing the above will simplify the installation and remove an obvious point of failure as users would only have to copy files to the root and profile directory and not have to add preferences to about:config.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant