Closed
Bug 357541
Opened 19 years ago
Closed 19 years ago
#searchInput setting ignored in userChrome.css if use Tiger mail theme
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: emoore, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061021 Thunderbird/2.0b1pre ID:2006102104
I added the following to userChrome.css in my chrome directory in my profile to change the width of the quick search text edit field. It had defaulted to only about a inch.
/*
* Change the width of the quick search text
*/
#searchInput {
width: 40em;
}
This worked using 1.5.0.7 under XP Pro SP2 using the Tiger mail 2.11 theme. It didn't work with version 2 beta 1 (20061020) or version 2 beta 1 (20061021) unless I either ran in safe mode or switched to a different theme. I checked it worked with the default theme and Nokia 2.0 eXtreme 2.30.
Other changes I made to userChrome.css such as eliminating the throbber worked regardless of what version or theme I used.
extensions.checkCompatibility is set to false. I needed to do that since using Nightly tester tools 1.2 to make everything compatible had no effect, in order to use that theme.
While this bug appears to be theme specific I'm reporting it since I was under the impression that setting should be changeable regardless of the theme.
Reproducible: Always
Comment 1•19 years ago
|
||
Have you tried #searchInput {
width: 40em !important;
} ?
Reporter | ||
Comment 2•19 years ago
|
||
Thanks for the suggestion. The problem doesn't occur if I use
#searchInput {
width: 40em !important;
}
or
#searchInput {
-moz-appearance: none !important;
width: 40em !important;
}
Comment 3•19 years ago
|
||
This is INVALID. You must use !important if you want to override a style that's already set.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•