Re: Seamonkey 2.x: Is is possible to disable / turn off / remove the "Set Default Browser" button?
Peter Potamus the Purple Hippo
> I already did a fair amount of digging but I can't find anything in
> about:config or via Google. Is it possible to disable / turn off /
> remove the "Set Default Browser" button using a lockPref setting or
> userChrome.css setting?
>
> - Thee Chicago Wolf [MVP]
I don't exactly understand what you mean by "lockPref"
but, to remove the button, in userChrome.css add the
following two lines:
#defaultBrowserButton
{display: none !important;}
The downside to this is if someone sets another browser
to the default, and you can't reset SM to the default
unless you remove the entry.
The other downside is some time down the road you can't
remember what happened to the default button ;-)
--
*IMPORTANT*: Sorry folks, but I cannot provide email
help!!!!
Warning: Private emails sent to me may become public
Peter Potamus & His Magic Flying Balloon:
http://melaman2.com/cartoons/singles/mp3/p-potamus.mp3
http://www.toonopedia.com/potamus.htm
Peter Potamus the Purple Hippo
>> Thee Chicago Wolf [MVP] wrote:
>>> I already did a fair amount of digging but I can't find anything in
>>> about:config or via Google. Is it possible to disable / turn off /
>>> remove the "Set Default Browser" button using a lockPref setting or
>>> userChrome.css setting?
>>>
>>> - Thee Chicago Wolf [MVP]
>> I don't exactly understand what you mean by "lockPref"
>> but, to remove the button, in userChrome.css add the
>> following two lines:
>>
>> #defaultBrowserButton
>> {display: none !important;}
>>
>> The downside to this is if someone sets another browser
>> to the default, and you can't reset SM to the default
>> unless you remove the entry.
>>
>> The other downside is some time down the road you can't
>> remember what happened to the default button ;-)
>
>
> Thanks kindly for the tip on this. It's changed slightly from how
> Seamonkey 1.1.x used to be.
thats for sure. Thats why I'm still sticking with SM 1
> Is there a big list of these options published somewhere?
you might try looking through this:
http://www.seamonkey-project.org/releases/seamonkey2.0/
> I'm also
> looking for how to disable/remove the "Manage add-ons..." button in
> Firefox. Lot of Google searches turned up zero.
what exact button are you referring to?
>
> When I was talking about lockPref, I was referring to the method of
> using a custom config file (i.e., seamonkey.cfg), running byteshifter
> on it, and creating an entry in all.js to point to the config file
> (i.e., pref("general.config.filename", "seamonkey.cfg");.
>
> Items in the config file that have lockPref (i.e.,
> lockPref("browser.startup.homepage", "http://www.somewebsite.com");)
> are then greyed out when a user tries to change a preference in either
> Firefox or Seamonkey. It's similar to the ancient client customization
> kit that Netscape used to have to lock users out of changing settings.
>
> - Thee Chicago Wolf [MVP]
never heard of LockPref
Peter Potamus the Purple Hippo
>>> I'm also
>>> looking for how to disable/remove the "Manage add-ons..." button in
>>> Firefox. Lot of Google searches turned up zero.
>> what exact button are you referring to?
>
> default behavior of buttons (i.e., disable or enable them). There does
> not seem to be one for the Manage Add-ons button as there is for other
> buttons.
sorry, but I'm still a confused, what Manage
Addons-button? Perhaps if you had an image, then I
could help you out. If I knew what you were talking
about them I might know of a work around.
>For example, one can disable the install button for
> extensions via "extensions.hideInstallButton", true.
I didn't know about that.
>>> When I was talking about lockPref, I was referring to the method of
>>> using a custom config file (i.e., seamonkey.cfg), running byteshifter
>>> on it, and creating an entry in all.js to point to the config file
>>> (i.e., pref("general.config.filename", "seamonkey.cfg");.
>>>
>>> Items in the config file that have lockPref (i.e.,
>>> lockPref("browser.startup.homepage", "http://www.somewebsite.com");)
>>> are then greyed out when a user tries to change a preference in either
>>> Firefox or Seamonkey. It's similar to the ancient client customization
>>> kit that Netscape used to have to lock users out of changing settings.
>>>
>>> - Thee Chicago Wolf [MVP]
>> never heard of LockPref
>
> Huh!? It's been around for years! I first came to learn about it via
> Chris Ilias's blog back in 2005 and have been using it to do kiosk
> mode on SM 1.1.x since then. It's what most folks have gone to since
> the Netscape CCK died. You REALLY need to read this then:
> http://ilias.ca/blog/2005/03/locking-mozilla-firefox-settings and then
> http://www.pcc-services.com/kixtart/firefox-lockdown.html
>
> - Thee Chicago Wolf [MVP]
Never knew that stuff. Thanks for the tip!
Peter Potamus the Purple Hippo
> <peter.potamus.t...@gmail.com> wrote:
>
>> Thee Chicago Wolf [MVP] wrote:
>>>>> I'm also
>>>>> looking for how to disable/remove the "Manage add-ons..." button in
>>>>> Firefox. Lot of Google searches turned up zero.
>>>> what exact button are you referring to?
>>> There are often options in about: config that allow you change the
>>> default behavior of buttons (i.e., disable or enable them). There does
>>> not seem to be one for the Manage Add-ons button as there is for other
>>> buttons.
>> sorry, but I'm still a confused, what Manage
>> Addons-button? Perhaps if you had an image, then I
>> could help you out. If I knew what you were talking
>> about them I might know of a work around.
>
> add-ons), Manage Add-ons button.
>
> - Thee Chicago Wolf [MVP]
OK, gotcha now. Now I know where you are. I was
looking at Tools, Add-ons. Anyways, try putting this
in your userChrome.css file. It will get rid of the
whole Addon area for that section:
#addonsMgrGroup
{display: none !important;}