Closed Bug 575841 Opened 11 years ago Closed 10 years ago
Quick filter bar search results colors do not match high contrast black color scheme
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20100625 Firefox/3.6.6 (.NET CLR 3.5.30729) Build Identifier: Thunderbird 3.1 Set Windows color scheme to "High Contrast Black" Start Thunderbird Make sure there are messages to search in the current folder (such as inbox) Type a search string in the "Filter these messages" or "search all messages" field. Search results come out as white text on a white background. Reproducible: Always Steps to Reproduce: 1. see above 2. 3. Actual Results: See above Expected Results: Background colour should be black (Window background) as defined in the "Hogh Contrast Black" colour scheme.
I can confirm this. It is a major for me so I'm hoping it can be fixed quickly. I will try to add a screenshot. It also happens in the Quick Search. The same problem has been reported for Lightning/Calandar Bug 435096 which I'm also hoping can be fixed quickly.
is this seen also in v3.0? or did you skip from 2.0.x to 3.1? similar, but far worse than bug 549634 (at least comparing screen shots)
blocking-thunderbird3.1: --- → ?
Version: unspecified → 3.1
Yes. I used all the releases of 3.0.x up to 3.0.5 before going to 3.1. Had the problem with all of them.
Sorry. Ignore that last comment. I did use all the releases of 3.0.x but this problem is NEW with 3.1. (got confused with the bug I reported earlier today which started with 3.0 and is still present - concerns assigning apps to attachment types)
Andreas, can you take a look at this?
Assignee: nobody → nisses.mail
blocking-thunderbird3.1: ? → needed
I can confirm this. Fix coming up shortly!
Status: UNCONFIRMED → NEW
Ever confirmed: true
This bus is still present in TB 3.1.2, in case anyone needed to know! :)
This bug is still present in TB 3.1.2, if anyone needed to know! :)
(In reply to comment #9) > This bug is still present in TB 3.1.2, if anyone needed to know! :) The bug is still open and is tracked on our branch list. We don't need additional comments unless it has been fixed by something else. Thanks.
This unfortunately makes the filtering worse in non-a11y mode, since you won't get the nice stripe visuals in the background for none found for example. Is there anything like -moz-system-metric for HighContrast built into Gecko?
Comment on attachment 464058 [details] [diff] [review] working treeviews in a11y mode Asking for ui-review. Andrew said this probably don't need code review.
Attachment #464058 - Flags: ui-review?(clarkbw)
If there is a -moz-system-metric, using it would not fix this particular bug. High contrast mode != high contrast color theme. You need to compare the text color to black instead to decide which path to use.
Comment on attachment 464058 [details] [diff] [review] working treeviews in a11y mode This seems to take away from the non-a11y mode but I guess there's not much choice.
Attachment #464058 - Flags: ui-review?(clarkbw) → ui-review+
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 3.3a1
This has NOT been fixed and is still present in TB5. I could send another screen shot but it would be identical to the original one I psoted.
PS. Using Windows 7 64bit now.
BJ, can you file a new bug please? Please cite your theme. This bug won't be reopened because it already has a patch that landed long ago.
p.s. and please clarify whether you are referring to quick filter bar or search all messages. If search all messages is your issue, then please refer to Bug 549634 - [faceted search] Make faceted search results window handle High Contrast mode
Summary: When in search screen colors do not match high contrast black color scheme → Quick filter bar search results colors do not match high contrast black color scheme
Wayne, It's exactly as given in this closed bug. It's the Quick Filter Bar when used with the High Contrast Black theme. But this time under Win 7 instead of XP. It's exactly the same. I'll open a new bug report. Bruce
Where's the new bug? No build was shipped with this fixed.
You need to log in before you can comment on or make changes to this bug.