116806 - Classic skin Messnger Composer button images appear even though disabled

Status: VERIFIED WORKSFORME

(MailNews Core :: Composition, defect)

Description

[Tom Kaczmarski]

Using the following code in userChrome.css I disabled the button images for 
most of the components of Mozilla 0.97.  The code so far appears to work in 
every place, but in the Messenger Composer app.  It seems that using the same 
code Netscape 6.2 behaves correctly and removes the images, but Mozilla 0.97 
does not.

BTW, it would be nice if there were an option for this in the Preferences menu 
like there was is in Netscape 4.7, i.e. Show Toolbars as Images and Text, 
Images Only, or Text Only.  Some people like huge buttons, others consider them 
wasted real estate.  It would be nice if both sides could have their way. 
Outside of this Mozilla/Netscape is evolving into a SUPERB browser.

Customization Code:

/* Navigator */
#back-button > *,
#forward-button > *,
#reload-button > *,
#stop-button > *,
#print-button > *,
/* Messenger */
#button-getmsg > *,
#button-newmsg > *,
#button-reply > *,
#button-replyall > *,
#button-forward > *,
#button-file > *,
#button-next > *,
#button-delete > *,
#button-mark > *,
#button-print > *,
#button-stop > *,
/* Messenger Composer */
#button-send > *,
#button-address > *,
#button-attach > *,
#button-quote > *,
#spellingButton > *,
#button-save > *,
#button-stop > *
 {
    list-style-image: none !important;
 }

Comment 1

[[e-mail]]

I assume you're using the Classic skin, in which the following code will work:

.toolbarbutton-1 > .toolbarbutton-icon,
.toolbarbutton-1 > .toolbarbutton-menubutton-button > .toolbarbutton-icon {
  display: none;
}

#navigator-throbber {
  margin: 0 5px !important;
  list-style-image:
url("chrome://communicator/skin/brand/throbber16-single.gif") !important;
}

#navigator-throbber[busy="true"] {
  list-style-image: url("chrome://communicator/skin/brand/throbber16-anim.gif")
!important;
}

Comment 2

[[e-mail] (gone - use [e-mail] instead)]

If this didn't work, please reopen this bug.