You can hide the options behind some CSS, however the underlying
functionality will still exist unless you modify Firefox's core files.
I've hidden some UI elements in my deployment by creating a
"systemChrome.css" file that resides in the application directory and a
function that deletes on start-up any userChrome.css that may override it.

This should work for you:

*$FF_DIR\browser\chrome\systemChrome.css*

@namespace xul url("
http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul";);

/* Hide Applications in Options */
xul|richlistitem#category-application.category,
/* Hide Content control under Applications category */
xul|vbox#applicationsContent

{ display: none !important; }



You can use a DOM inspector to identify additional elements that you wish
to hide as well.

Then you will need to have Firefox load this CSS on startup since it's not
a default file.  Integrate this into your mozilla.cfg (or your equivalent):

*$FF_DIR\mozilla.cfg*

const {classes: Cc, interfaces: Ci, utils: Cu} = Components;
Cu.import("resource://gre/modules/FileUtils.jsm");

// Load system chrome CSS to block additional UI elements.
var css = Cc["@mozilla.org/content/style-sheet-service;1
"].getService(Ci.nsIStyleSheetService);
var ios = Cc["@mozilla.org/network/io-service;1
"].getService(Ci.nsIIOService);
var cssFile = FileUtils.getFile("AChrom", ["systemChrome.css"]);
var cssUri = ios.newFileURI(cssFile);
css.loadAndRegisterSheet(cssUri, 1);

// Delete user profile chrome directory.
var profChromDir = FileUtils.getDir("ProfD", ["chrome"]);
if ( profChromDir.exists() ) {
    profChromDir.remove(true);
}






On Wed, Jul 20, 2016 at 5:17 PM, Kaply Consulting <[email protected]>
wrote:

> There's no built in way to prevent users from modify the helper apps.
>
> You could add some custom code to disable the applications dialog
> completely.
>
> If you use the CCK2, you could hide that entire tab.
>
> Mike
>
> On Tue, Jul 19, 2016 at 7:45 AM, Hosley, Jamie (ESE) <[email protected]>
> wrote:
>
>> Hi Firefox ESR Group,
>>
>> We’re currently working on an enterprise wide deployment of Firefox ESR
>> and we’d like to lock the user from making changes to the Applications
>> selections in Options. We have a mimetypes.rdf file configured with the app
>> choice settings we want and everything set for the default profile to be
>> built, but I’m looking for how to lock the user from access to the
>> Applications area in options, is there way to do that? Any info would be
>> appreciated.
>>
>> Thanks,
>>
>> Jamie
>>
>> ----------------------------
>>
>> Jamie Hosley
>>
>> VA Enterprise Systems Engineering
>>
>> Client Services Desktop Technologies
>>
>>
>>
>> _______________________________________________
>> Enterprise mailing list
>> [email protected]
>> https://mail.mozilla.org/listinfo/enterprise
>>
>> To unsubscribe from this list, please visit
>> https://mail.mozilla.org/listinfo/enterprise or send an email to
>> [email protected] with a subject of "unsubscribe"
>>
>
>
> _______________________________________________
> Enterprise mailing list
> [email protected]
> https://mail.mozilla.org/listinfo/enterprise
>
> To unsubscribe from this list, please visit
> https://mail.mozilla.org/listinfo/enterprise or send an email to
> [email protected] with a subject of "unsubscribe"
>
_______________________________________________
Enterprise mailing list
[email protected]
https://mail.mozilla.org/listinfo/enterprise

To unsubscribe from this list, please visit 
https://mail.mozilla.org/listinfo/enterprise or send an email to 
[email protected] with a subject of "unsubscribe"

Reply via email to