284432 - Mail menu cannot be disabled from userChrome.css

Status: RESOLVED DUPLICATE of bug 261917

(Firefox :: Menus, defect)

Description

[Onno Ekker [:nONoNonO UTC+1]]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

Please add an id to the browser.jar/content/browser/browser.xul for the menuitem
 label="&mailButton.readMail.label" to be able to disable this item by only
specifying the id in userChrome.css. Otherwise you need to disabled by label,
but the label is variable (number of new messages).
While you`re at it, please also add an id to the menuseparator to also hide
that. It's better when you don't display both the Read mail (0 new)... and New
Message menuitems to also hide a seperator line...

Reproducible: Always




I posted this bug as minor: easy workaround.
Now I need to edit the browser.xul file myself after each new version.
But the fix should be just as easy, with the addes benefit that it works for
everybody. It's somewhere around line 850...

Comment 1

[PikeUK]

How about:

menuitem[label^="Read Mail ("] {display: none !important;}

or:

menuitem[command="Browser:ReadMail"] {display: none !important;}

Comment 2

[Onno Ekker [:nONoNonO UTC+1]]

Cool! Does that work too? And how to disable the double seperator line when I
hide both ReadMail and NewMessage?

The next menuseperator had an id (devToolsSeparator), so why not add an
devMailSeparator too...

Comment 3

[PikeUK]

(In reply to comment #2)
> Cool! Does that work too? And how to disable the double seperator line when I
> hide both ReadMail and NewMessage?
> 
> The next menuseperator had an id (devToolsSeparator), so why not add an
> devMailSeparator too...

Just add "+ menuseparator" after whatever rule you use to hide the New Message
item, e.g.:

menuitem[command="Browser:NewMessage"] + menuseparator {display: none !important;}

Comment 4

[Nickolay_Ponomarev]

Since this particular problem has been resolved, I'm duping it to a more general
bug.

Onno: you can try Menu Editor extension for easier manipulation of menus.

*** This bug has been marked as a duplicate of 261917 ***