Re: Using userContent.css to hide about:support and about:plugins

[»Q«]

In
<news:mailman.1068.142870727...@lists.mozilla.org>,
"Thee Chicago Wolf [MVP]" <"."@.> wrote:

> Presently, my userContent.css file is set up like so:
>
> #addons-page,
> div#contents button,
> window#config * {display:none !important;}
>
> It hides what I don't want users messing with well enough but I also
> wouldn't mind hiding about:support and about:plugins. I tried adding
> window#support * but it didn't make any difference. Probably the wrong
> element. Tried finding it with Element Inspector but it wasn't of much
> use. Google points to some info
> (https://support.mozilla.org/en-US/questions/1001724) which doesn't
> work either.
>
> Anyone have some solid info on hiding these two menus?

This should work:

@-moz-document url("about:support") { * { display : none ! important } }

Or for a more comprehensive approach:

@-moz-document url-prefix("about:") { * { display : none ! important } }

I'm assuming the Firefoxes you want to cripple belong to you, not the
users you want to prevent seeing things.

[EE]

Thee Chicago Wolf [MVP] wrote:
> Presently, my userContent.css file is set up like so:
>
> #addons-page,
> div#contents button,
> window#config * {display:none !important;}
>
> It hides what I don't want users messing with well enough but I also
> wouldn't mind hiding about:support and about:plugins. I tried adding
> window#support * but it didn't make any difference. Probably the wrong
> element. Tried finding it with Element Inspector but it wasn't of much
> use. Google points to some info
> (https://support.mozilla.org/en-US/questions/1001724) which doesn't
> work either.
>
> Anyone have some solid info on hiding these two menus?
>

> - Thee Chicago Wolf [MVP]
>
Are you sure that is userContent.css and not userChrome.css?

[»Q«]

In
<news:mailman.1175.142880227...@lists.mozilla.org>,
"Thee Chicago Wolf (MVP)" <"."@.> wrote:

> On Sat, 11 Apr 2015 12:22:55 -0700, EE <nu...@bees.wax> wrote:
>
> >Thee Chicago Wolf [MVP] wrote:
> >> Presently, my userContent.css file is set up like so:
> >>
> >> #addons-page,
> >> div#contents button,
> >> window#config * {display:none !important;}
> >>
> >> It hides what I don't want users messing with well enough but I
> >> also wouldn't mind hiding about:support and about:plugins. I tried
> >> adding window#support * but it didn't make any difference.
> >> Probably the wrong element. Tried finding it with Element
> >> Inspector but it wasn't of much use. Google points to some info
> >> (https://support.mozilla.org/en-US/questions/1001724) which doesn't
> >> work either.
> >>
> >> Anyone have some solid info on hiding these two menus?

> >Are you sure that is userContent.css and not userChrome.css?
>

> Well, I didn't try in userChrome.css but what info I gleaned via
> Google points to userContent. I'll give it a shot.

userChrome.css won't restyle about: pages.

[Ron K.]

Wolf seems to want hiding of Chrome menu options which are userChrome.css
styled items.

There are some articles at mozillazine in their knowledge base related to
menu modification.

--
Ron K.
Who is General Failure, and why is he searching my HDD?
Kernel Restore reported Major Error used BSOD to msg the enemy!

[»Q«]

In
<news:mailman.1280.142895039...@lists.mozilla.org>,

"Thee Chicago Wolf [MVP]" <"."@.> wrote:

> On Fri, 10 Apr 2015 21:48:29 -0500, »Q« <box...@gmx.net> wrote:

> >@-moz-document url-prefix("about:") { * { display : none !
> >important } }
> >
> >I'm assuming the Firefoxes you want to cripple belong to you, not the
> >users you want to prevent seeing things.
>

> Just out of curiosity, how did you garner this info?

I think I first learned about @-moz-document from a blog post when it
was implemented, but that's too far in the long ago for me to
remember. What documentation there is for it is at
<https://developer.mozilla.org/docs/Web/CSS/@document>. I didn't know
if it would work for "about:" until I tried it.

Down the road, they plan to move a lot of stuff to in-content pages,
like about:downloads, so it might someday become too much to clobber
all about: pages. But with "@-moz-document url(about:whatever)" you
should be able to deal with them one by one.