Closed
Bug 606735
Opened 14 years ago
Closed 13 years ago
aero basic tabstrip picking up the wrong color.
Categories
(Firefox :: Theme, defect)
Tracking
()
VERIFIED
FIXED
Firefox 4.0b12
Tracking | Status | |
---|---|---|
blocking2.0 | --- | - |
People
(Reporter: asa, Assigned: dao)
References
Details
(Keywords: polish)
Attachments
(3 files, 2 obsolete files)
74.65 KB,
image/png
|
Details | |
109.95 KB,
image/jpeg
|
Details | |
3.88 KB,
patch
|
beltzner
:
approval2.0+
|
Details | Diff | Splinter Review |
Ideally the tabstrip background color would blend with the titlebar color. Right now it looks kinda bad.
Reporter | ||
Comment 1•14 years ago
|
||
I believe that the current look works fine for the tabs on bottom case but not for the tabs on top (which I believe is the default). Hopefully we can get it right for both cases.
Reporter | ||
Comment 2•14 years ago
|
||
The closer I look at this, the more I think that for tabs on top, the tab strip simply needs to be transparent like it is for the glass theme. The window frame color/gradient is correct behind it.
Assignee | ||
Comment 3•14 years ago
|
||
(In reply to comment #2) > The closer I look at this, the more I think that for tabs on top, the tab strip > simply needs to be transparent like it is for the glass theme. The window frame > color/gradient is correct behind it. There's just gray behind the tab strip, and I don't think the color we'd want her is currently accessible or covered by native rendering.
I made this and using stylish works well: @media all and (-moz-windows-default-theme) { #navigator-toolbox[tabsontop="false"] > toolbar:not(:-moz-lwtheme), #TabsToolbar[tabsontop="true"]:not(:-moz-lwtheme) { background: rgb(185,209,234) !important; } #navigator-toolbox[tabsontop="false"] > toolbar:-moz-window-inactive:not(:-moz-lwtheme),#TabsToolbar[tabsontop="true"]:-moz-window-inactive:not(:-moz-lwtheme) { background: rgb(215,228,242) !important; } } @media all and (-moz-windows-compositor) { #navigator-toolbox[tabsontop="false"] > toolbar:not(:-moz-lwtheme), #TabsToolbar[tabsontop="true"]:not(:-moz-lwtheme) { background: transparent !important; } #navigator-toolbox[tabsontop="false"] > toolbar:-moz-window-inactive:not(:-moz-lwtheme),#TabsToolbar[tabsontop="true"]:-moz-window-inactive:not(:-moz-lwtheme) { background: transparent !important; } }
This should block final in my view. The Aero Basic theme is negligible on normal desktop systems, but don't forget the netbooks. Nearly every Windows 7 netbook runs with Aero Basic, instead of Aero Glass.
Assignee | ||
Updated•13 years ago
|
blocking2.0: --- → ?
Assignee | ||
Comment 6•13 years ago
|
||
Assignee: nobody → dao
Status: NEW → ASSIGNED
Comment 7•13 years ago
|
||
Hard to notice on Aero Basic machines, would approve a patch, but not gonna block on it.
blocking2.0: ? → -
Keywords: polish
Assignee | ||
Comment 8•13 years ago
|
||
Attachment #510081 -
Attachment is obsolete: true
Attachment #512018 -
Flags: review?(felipc)
Comment 9•13 years ago
|
||
Comment on attachment 512018 [details] [diff] [review] patch This looks beautiful! To simplify these rules a bit I'd really vote for adding an !important rule for the menubar-autohide binding in xul.css http://mxr.mozilla.org/mozilla-central/source/toolkit/content/xul.css#279 This would get rid of all the autohide selectors here and it doesn't seem wrong to me (helps avoid a menu with the autohide attribute and a possible incorrect binding) I understand though if you prefer not to make xul.css changes for this. In this case, we can still get rid of the autohides by dropping the first rule: + #toolbar-menubar:not([autohide=true]):not(:-moz-lwtheme):-moz-system-metric(windows-default-theme), as we don't support custom drag areas for windows without custom titlebar drawing yet. I didn't find a situation where the !important markers for the background-color here are required.
Assignee | ||
Comment 10•13 years ago
|
||
(In reply to comment #9) > To simplify these rules a bit I'd really vote for adding an !important rule for > the menubar-autohide binding in xul.css > http://mxr.mozilla.org/mozilla-central/source/toolkit/content/xul.css#279 > This would get rid of all the autohide selectors here and it doesn't seem wrong > to me (helps avoid a menu with the autohide attribute and a possible incorrect > binding) > > I understand though if you prefer not to make xul.css changes for this. I'd rather not. We usually don't override or extend the autohide binding, but somebody else might want to. > In this > case, we can still get rid of the autohides by dropping the first rule: > > + > #toolbar-menubar:not([autohide=true]):not(:-moz-lwtheme):-moz-system-metric(windows-default-theme), > > as we don't support custom drag areas for windows without custom titlebar > drawing yet. That's a pretty annoying bug (it affects the stock downloads manager), and I don't think we should remove correct selectors for it. It's also sort of a regression, as this used to work at least without aero snap support. > I didn't find a situation where the !important markers for the background-color > here are required. I'll look into this.
Assignee | ||
Comment 11•13 years ago
|
||
Ok, !important isn't needed for the background-color. I think we should keep the rest as is, though.
Comment 12•13 years ago
|
||
Comment on attachment 512018 [details] [diff] [review] patch Alright then let's just remove the !important from the background-color
Attachment #512018 -
Flags: review?(felipc) → review+
Assignee | ||
Comment 13•13 years ago
|
||
removed !important
Attachment #512018 -
Attachment is obsolete: true
Attachment #512588 -
Flags: approval2.0?
Comment 14•13 years ago
|
||
Comment on attachment 512588 [details] [diff] [review] patch a=beltzner
Attachment #512588 -
Flags: approval2.0? → approval2.0+
Assignee | ||
Comment 15•13 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/a4784c581b3f
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 4.0b12
Comment 16•13 years ago
|
||
Mozilla/5.0 (Windows NT 6.1; rv:2.0b12pre) Gecko/20110216 Firefox/4.0b12pre Verified issue and it's no longer present.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•