Allow user.js to set default search engine

[KERR]

A user.js file is handy for configuring Firefox settings, especially for mass deployment and/or to save having to hunt through about:config etc.

As far as I'm aware, you're restricted from setting the search engine via user.js or even about:config, even though you can set almost any/every other setting this way.

From memory it was restricted due to concerns of mis-use.

Hoping we can get the functionality revisited 👍

[Jon]

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.

[Standard8]

If you are deploying to an enterprise, then you should use the enterprise distributions with enterprise policies set-up. See here for more information: https://www.mozilla.org/firefox/enterprise/

[sooc]

It would be appreciated if this feature were reinstated at some point.

I have a situation that isn't quite enterprise but one where we try and ship more sensible defaults. Part of that is setting DuckDuckGo over Google so users have access to search bangs. We also collapse the tabs toolbar as well as the navigator toolbox so access to about:preferences#search isn't possible. This is done to remove distractions and utilize more of the limited screen space for content.

Still, the ideal is to have the setting already populated to the group preference regardless of any changes to user chrome styles.

Anyway, +1 for letting users configure their browser.

[Standard8]

> I have a situation that isn't quite enterprise but one where we try and ship more sensible defaults. Part of that is setting DuckDuckGo over Google so users have access to search bangs. We also collapse the tabs toolbar as well as the navigator toolbox so access to about:preferences#search isn't possible. This is done to remove distractions and utilize more of the limited screen space for content.

I'm curious as to why Enterprise doesn't fit your use case. Presumably you are handling this in a company environment?