From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Firefox/1.0.2 Fedora/1.0.2-1.3.1
Description of problem:
I have a grey background in the preview text area and the compose window, this is new for this version, I did not see it in earlier versions. From what I can see this only affects non-html mails, i.e. html mails display the colors set in edit->preferences->display
The rpm changelog says:
* Wed Mar 23 2005 Christopher Aillon <firstname.lastname@example.org> 1.0.2-1.3.1
- Thunderbird 1.0.2
- Enable pango rendering
I suppose this has something to do with pango.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start thunderbird
2. Make one mail visable in the preview window, or start the compose window
Actual Results: The text area have a grey background
Expected Results: The text area should have a white background (as in former versions.)
Tried both my regular account, and a new one where I had not used Thunderbird before, same results in both cases, i.e. no old data laying around creating problems.
same problem here...
this has nothing to do with pango
to prefs.js solves the problem.
same for me
will work. So it is fixed.:)
Adding user_pref("browser.display.use_system_colors",false); to prefs.js works.
But this really, IMHO, should be a tick box in edit->preferences->display (as is
the case in Firefox)
If the grey background differentiates a "plain text" message from an "html"
message, I like it... :-)
I agree with Lars... if adding to prefs.js is the solution here, then why do we
need a gui interface at all for other options?
How many other user preferences are only available by editting prefs.js?
I agree it is an acceptable work-around, but not a solution.
This is just me being dumb. I merged in that pref to make thunderbird get the
colors from GTK, but forgot to merge in the patch for making it ask GTK for the
right color. Building a new one now.
Fixed for me (FFM?) in 1.0.2-1.3.2.
Resolved->ISUCK. sorry about the issues.
It seems that the Mozilla update has the same problem!