GNOME Bugzilla – Bug 206032
Text unreadable when selecting message [theme conflict]
Last modified: 2005-11-15 02:22:21 UTC
Package: Evolution Priority: Normal Version: 0.12.99 Synopsis: Text unreadable when selecting message. Bugzilla-Product: Evolution Bugzilla-Component: Mailer Description: When you select a message from the INBOX, or any other folder to read, then you can no longer read the text. I am using Ximian GNOME 1.4 with Nautilus. I am using the Eazel Blue theme, and this is where the problem seems to lie. When I traverse a menu in Evolution, the highlight is dark blue, but the text changes from black to white, thus allowing you to read it. The text in the message pane stays black, and therefore, the dark blue obscures the text. Unknown reporter: andrig.t.miller@megapathdsl.net, changed to bugbuddy-import@ximian.com.
Similar bugs have been reported before but I'm not sure if they've been marked for UI.
This due to a combination of the eazel-blue theme being lax about what colors it sets and differences in the way gtkhtml and etext choose colors. I'm attaching a patch to the eazel-blue theme that works around the problem. Deciding if this is the right place to fix it is slightly more involed. I hate the design of gtk themes.
Created attachment 40111 [details] [review] fix eazel-blue selection color
The change to the Eazel-blue theme definitely did work. Thanks. Of course, if this isn't the long-term fix, I will definitely be interested. Thanks.
*** bug 206522 has been marked as a duplicate of this bug. ***
cc'ing distribution bugs; it would be nice if they could patch the themes we distribute. Don't know if they will or can within their policies, though.
As a result of the UI freeze today, I'm marking all remaining non-1.0 UI bugs to 'future'. Someone reading this should only change the target back to 1.0 under the following circumstances: 1) The change would not impact documentation. (i.e., 'how to do X' would not have to be changed in any way.) 2) The change would require trivial work for the programmers involved. Most likely, only the programmers themselves are able to judge this. So, if you are not on the evo team, or cannot provide a patch to them for this, you should probably not make any such changes. Sorry that this is going to impact so many irritating bugs, but we have to prioritize our limited resources.
*** bug 222169 has been marked as a duplicate of this bug. ***
I don't think this bug has the right to live, so slaying it.
*** bug 234502 has been marked as a duplicate of this bug. ***