Closed
Bug 986324
Opened 12 years ago
Closed 12 years ago
Text inputs (URL and search bar) are unreadable in the nav-bar in High Contrast Mode
Categories
(Firefox :: Theme, defect)
Tracking
()
VERIFIED
FIXED
Firefox 31
People
(Reporter: MattN, Assigned: mikedeboer)
References
Details
(Keywords: access, regression, Whiteboard: [Australis:P3-])
Attachments
(2 files, 3 obsolete files)
|
19.47 KB,
image/png
|
Details | |
|
4.30 KB,
patch
|
dao
:
review+
Sylvestre
:
approval-mozilla-aurora+
Sylvestre
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
This is about a regression since bug 963950 was filed and is of higher priority since it's a usability regression. I saw it reported on input today. The text in the address and search bars are yellow on a white background which isn't readable at all on Windows 8 with High Contrast #1.
Last good revision: 41d962d23e81 (2014-03-11)
First bad revision: 44ae8462d6ab (2014-03-12)
Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=41d962d23e81&tochange=44ae8462d6ab
Prior to this regression, it was still yellow text but on a black input background (much more contrast).
| Reporter | ||
Comment 2•12 years ago
|
||
Specifically https://hg.mozilla.org/mozilla-central/rev/ece9cdfb15d7
I see the background of the URL and search field is getting its background color set
Comment 3•12 years ago
|
||
(In reply to Matthew N. [:MattN] from comment #2)
> Specifically https://hg.mozilla.org/mozilla-central/rev/ece9cdfb15d7
>
> I see the background of the URL and search field is getting its background
> color set
Yes. This needs to use -moz-windows-default-theme, like here: http://hg.mozilla.org/mozilla-central/annotate/c148f0b0c8b4/browser/themes/windows/browser.css#l1075
I'm not sure either why such a large Win8-specific block had to be added rather than modifying / refactoring the url and search bar styles we already had. Note that we had previously /removed/ the background transparency from these fields on Windows Vista and 7. Introducing it again on Windows 8 (which is visually simpler than the former versions) seems backwards.
Assignee: nobody → mdeboer
Component: Disability Access → Theme
| Assignee | ||
Comment 5•12 years ago
|
||
Attachment #8396470 -
Flags: review?(jaws)
| Assignee | ||
Comment 6•12 years ago
|
||
Updated•12 years ago
|
Attachment #8396470 -
Flags: review?(jaws) → review?(dao)
| Assignee | ||
Comment 7•12 years ago
|
||
Dão, one thing that might interest you is that `(-moz-windows-default-theme)` evaluates to true when a high contrast theme is selected on Windows 8. Is that expected and if not, should I file a bug?
Status: NEW → ASSIGNED
| Assignee | ||
Comment 8•12 years ago
|
||
(In reply to Mike de Boer [:mikedeboer] from comment #7)
> Dão, one thing that might interest you is that
> `(-moz-windows-default-theme)` evaluates to true when a high contrast theme
> is selected on Windows 8. Is that expected and if not, should I file a bug?
Alright, this is bug 946595.
Depends on: 946595
Comment 9•12 years ago
|
||
Comment on attachment 8396470 [details] [diff] [review]
Patch v1: small refactor of urlbar and search field styles
> #urlbar:not(:-moz-lwtheme)[focused],
> .searchbar-textbox:not(:-moz-lwtheme)[focused] {
>- border-color: hsla(206,100%,60%,.65) hsla(206,100%,55%,.65) hsla(206,100%,50%,.65);
>+ border-color: #4595e5;
> }
Can you use 'highlight' here?
>+ #urlbar:not(:-moz-lwtheme),
>+ .searchbar-textbox:not(:-moz-lwtheme) {
>+ background-color: -moz-field;
Why are you setting background-color:-moz-field here? What background color is used with this line removed?
>+ box-shadow: none;
>+ transition-duration: 0s;
>+ }
Why should the box-shadow and the border-color transition be there on Windows 8 but not on Windows Vista and 7?
>+ .chatbar-button,
>+ chatbar > chatbox {
>+ border-color: #A9B7C9;
>+ }
Hm, we should probably do this on Windows 8 too.
Attachment #8396470 -
Flags: review?(dao) → review-
Comment 10•12 years ago
|
||
(In reply to Dão Gottwald [:dao] from comment #9)
> Comment on attachment 8396470 [details] [diff] [review]
> Patch v1: small refactor of urlbar and search field styles
>
> > #urlbar:not(:-moz-lwtheme)[focused],
> > .searchbar-textbox:not(:-moz-lwtheme)[focused] {
> >- border-color: hsla(206,100%,60%,.65) hsla(206,100%,55%,.65) hsla(206,100%,50%,.65);
> >+ border-color: #4595e5;
> > }
>
> Can you use 'highlight' here?
#4595e5 is a deeper blue than highlight. I think what would be best is to create a media query to target specifically the high contrast theme. IE has this.
Comment 11•12 years ago
|
||
(In reply to Tim Nguyen [:ntim] from comment #10)
> > > #urlbar:not(:-moz-lwtheme)[focused],
> > > .searchbar-textbox:not(:-moz-lwtheme)[focused] {
> > >- border-color: hsla(206,100%,60%,.65) hsla(206,100%,55%,.65) hsla(206,100%,50%,.65);
> > >+ border-color: #4595e5;
> > > }
> >
> > Can you use 'highlight' here?
> #4595e5 is a deeper blue than highlight.
There is a slight difference, yes, but this begs the question why we're deviating from the platform default.
> I think what would be best is to
> create a media query to target specifically the high contrast theme. IE has
> this.
This rule isn't used for high contrast themes.
Comment 12•12 years ago
|
||
(In reply to Dão Gottwald [:dao] from comment #11)
> (In reply to Tim Nguyen [:ntim] from comment #10)
> > > > #urlbar:not(:-moz-lwtheme)[focused],
> > > > .searchbar-textbox:not(:-moz-lwtheme)[focused] {
> > > >- border-color: hsla(206,100%,60%,.65) hsla(206,100%,55%,.65) hsla(206,100%,50%,.65);
> > > >+ border-color: #4595e5;
> > > > }
> > >
> > > Can you use 'highlight' here?
> > #4595e5 is a deeper blue than highlight.
>
> There is a slight difference, yes, but this begs the question why we're
> deviating from the platform default.
Well, MS hasn't updated some of the system values we use since Windows XP/2000 (-moz-dialog, -moz-field, ThreeDShadow and some more I think). So we can't keep using these forever, really.
Maybe we should even build our own system values, made for Australis, all by supporting high contrast. It would fix inconsistency issues, and also give the opportunity for us to be free with our UI. Chrome did this (with the Aura project), and replaced all system native dialogs/colors/controls by their own.
Comment 13•12 years ago
|
||
(In reply to Dão Gottwald [:dao] from comment #11)
> (In reply to Tim Nguyen [:ntim] from comment #10)
> There is a slight difference, yes, but this begs the question why we're
> deviating from the platform default.
>
> > I think what would be best is to
> > create a media query to target specifically the high contrast theme. IE has
> > this.
>
> This rule isn't used for high contrast themes.
Yes, but I meant using #4595e5 for default Windows 8 theme, and Highlight for the high contrast ones.
Comment 14•12 years ago
|
||
(In reply to Tim Nguyen [:ntim] from comment #12)
> > > > Can you use 'highlight' here?
> > > #4595e5 is a deeper blue than highlight.
> >
> > There is a slight difference, yes, but this begs the question why we're
> > deviating from the platform default.
>
> Well, MS hasn't updated some of the system values we use since Windows
> XP/2000 (-moz-dialog, -moz-field, ThreeDShadow and some more I think). So we
> can't keep using these forever, really.
That's not true, neither for the ones you cited nor for 'highlight'.
Comment 15•12 years ago
|
||
(In reply to Dão Gottwald [:dao] from comment #14)
> (In reply to Tim Nguyen [:ntim] from comment #12)
> > > > > Can you use 'highlight' here?
> > > > #4595e5 is a deeper blue than highlight.
> > >
> > > There is a slight difference, yes, but this begs the question why we're
> > > deviating from the platform default.
> >
> > Well, MS hasn't updated some of the system values we use since Windows
> > XP/2000 (-moz-dialog, -moz-field, ThreeDShadow and some more I think). So we
> > can't keep using these forever, really.
>
> That's not true, neither for the ones you cited nor for 'highlight'.
Highlight used to be darker on Windows XP. But for the ones I cited, I've barely seen a difference.
| Assignee | ||
Comment 16•12 years ago
|
||
Addressed all review comments.
* border-color is now Highlight, their transition stays in Aero too.
* Moved Social styles to apply for Win8 too.
Attachment #8396470 -
Attachment is obsolete: true
Attachment #8400751 -
Flags: review?(dao)
| Assignee | ||
Comment 17•12 years ago
|
||
Hmm, I forgot to remove the `box-shadow: none`... if you want it applied on Vista/ Win 7, then I'll remove the rule entirely.
Comment 18•12 years ago
|
||
(In reply to Mike de Boer [:mikedeboer] from comment #16)
> * Moved Social styles to apply for Win8 too.
Ooop, I cited the wrong code. I actually meant this:
+ .menu-accel,
+ .menu-iconic-accel {
+ color: graytext;
+ }
I have no idea whether the chatbar stuff should apply for Windows 8.
Comment 19•12 years ago
|
||
(In reply to Mike de Boer [:mikedeboer] from comment #17)
> Hmm, I forgot to remove the `box-shadow: none`... if you want it applied on
> Vista/ Win 7, then I'll remove the rule entirely.
Makes sense to me.
| Assignee | ||
Comment 20•12 years ago
|
||
Left the Social styles like the previous patch; better to be safe than sorry.
Attachment #8396471 -
Attachment is obsolete: true
Attachment #8400751 -
Attachment is obsolete: true
Attachment #8400751 -
Flags: review?(dao)
Attachment #8401263 -
Flags: review?(dao)
Updated•12 years ago
|
Attachment #8401263 -
Flags: review?(dao) → review+
| Assignee | ||
Comment 21•12 years ago
|
||
status-firefox29:
--- → affected
status-firefox30:
--- → affected
status-firefox31:
--- → affected
Whiteboard: [Australis:P3-] → [Australis:P3-][fixed-in-fx-team]
Comment 22•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [Australis:P3-][fixed-in-fx-team] → [Australis:P3-]
Target Milestone: --- → Firefox 31
| Assignee | ||
Updated•12 years ago
|
| Assignee | ||
Comment 23•12 years ago
|
||
Comment on attachment 8401263 [details] [diff] [review]
Patch v3: small refactor of urlbar and search field styles
[Approval Request Comment]
Bug caused by (feature/regressing bug #): Bug 960517, Australis.
User impact if declined: With a High Contrast theme enabled in Windows 8.x, the entered text in the urlbar and/ or search field are hard to read. This patch fixes that.
Testing completed (on m-c, etc.): landed on m-c.
Risk to taking this patch (and alternatives if risky): minor
String or IDL/UUID changes made by this patch: n/a
Attachment #8401263 -
Flags: approval-mozilla-beta?
Attachment #8401263 -
Flags: approval-mozilla-aurora?
Updated•12 years ago
|
Attachment #8401263 -
Flags: approval-mozilla-beta?
Attachment #8401263 -
Flags: approval-mozilla-beta+
Attachment #8401263 -
Flags: approval-mozilla-aurora?
Attachment #8401263 -
Flags: approval-mozilla-aurora+
Comment 24•12 years ago
|
||
Comment 25•12 years ago
|
||
this seems to cause a tart regression:
http://graphs.mozilla.org/graph.html#tests=[[293,132,31]]&sel=none&displayrange=30&datatype=running
in general we went from ~6.30 -> ~6.44, this is small, but a regression nonetheless.
here is a tbpl view with some retriggers before/after:
https://tbpl.mozilla.org/?tree=Fx-Team&fromchange=50d49ff44ddf&tochange=5da838032667&jobname=WINNT%206.2%20fx-team%20talos%20svgr
Comment 26•12 years ago
|
||
Joel, bugs usually stay resolved unless the patches were ineffective or got backed out.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Comment 27•12 years ago
|
||
Apologies :dao. I had received feedback that opening new bugs was confusing- I think it is not always the case.
Comment 28•12 years ago
|
||
(In reply to Dão Gottwald [:dao] from comment #26)
> Joel, bugs usually stay resolved unless the patches were ineffective or got
> backed out.
We're trying to evaluate how to handle talos regressions, the discussion is at bug 990644.
The current options are, per talos regression: file a new bug, reopen the possibly offending bug, or needinfo the owner on the possibly offending bug.
Please post your inputs to bug 990644, thanks.
Comment 29•12 years ago
|
||
The text inputs from the URL bar and the search bar are now visible while using High Contrast Mode on Windows 8.
Verified using:
- latest Nightly, build ID: 20140410030200
- latest Aurora, build ID: 20140410004003
- Fx 29 beta 7, build ID: 20140410150427
Status: RESOLVED → VERIFIED
Keywords: verifyme
You need to log in
before you can comment on or make changes to this bug.
Description
•