Closed
Bug 352678
Opened 19 years ago
Closed 18 years ago
Ugly shade of blue as location bar and search bar border instead of native colors
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
FIXED
Firefox 3 beta1
People
(Reporter: marcoos, Assigned: dao)
References
Details
Attachments
(3 files)
|
63.59 KB,
image/png
|
Details | |
|
156.08 KB,
image/png
|
Details | |
|
4.81 KB,
patch
|
asaf
:
review+
mconnor
:
approval1.9+
|
Details | Diff | Splinter Review |
This is a regression in the new theme on Linux.
Both the location bar and the search bar borders should use GTK colors. For example, when using the Gilouche GTK theme (default in Novell SLED and OpenSUSE's GNOME), the border should be #bca775, but it's #96969d.
This was correct in 1.5 and before the theme changes in 2.0.
Also, on focus the border color also should change to another one, though this wasn't working 1.5.
| Reporter | ||
Comment 1•19 years ago
|
||
Latest tinderbox build and another GTK app for comparison.
| Assignee | ||
Comment 2•19 years ago
|
||
That's because it was decided that the border should match the end caps (bug 351195). I favored using ThreeDShadow instead of #96969d, but I was alone.
| Reporter | ||
Comment 3•19 years ago
|
||
Oh, so this was done on purpose? :-o
Comment 4•19 years ago
|
||
Count me in as Marek's backup. I don't want to enforce my hatred for non-standard colors/widgets on anyone. But I HATE when others enforce their "my widgets are better" position on me.
I've chosen a GTK theme. Now please respect my choice and use the standard colors, please...
In the screenshot attached, the problem of input look is even more apparent. And I'll pretend not to see what's been done with tabs. :)
Comment 5•19 years ago
|
||
If the endcaps can be made to automatically use system colors in their borders, we can certainly change this. Regardless, though, the endcaps and the rest of the border need to match -- a consistent, non-native color is better than having pieces of the line be one color and pieces be another.
Since the endcaps are images, this is going to be a bit difficult to get right. Dao has had some ideas that might be suitable for trunk. This will not be changed in Firefox 2.
| Reporter | ||
Comment 6•19 years ago
|
||
Can't you use CSS borders and -moz-border-radius for the endcap?
| Assignee | ||
Comment 7•19 years ago
|
||
(In reply to comment #6)
> Can't you use CSS borders and -moz-border-radius for the endcap?
I did try that (bug 351195 comment 31). With Gecko 1.8, border-radius is too jittery.
| Assignee | ||
Updated•18 years ago
|
| Assignee | ||
Updated•18 years ago
|
Target Milestone: --- → Firefox 3
Version: unspecified → 2.0 Branch
| Assignee | ||
Comment 8•18 years ago
|
||
Comment 9•18 years ago
|
||
Comment on attachment 280992 [details] [diff] [review]
use ThreeDShadow
r=mano
Attachment #280992 -
Flags: review?(mano) → review+
| Assignee | ||
Updated•18 years ago
|
Attachment #280992 -
Flags: approval1.9?
| Assignee | ||
Updated•18 years ago
|
OS: Linux → All
Summary: Ugly shade of blue as location bar and search bar border instead of GTK colors → Ugly shade of blue as location bar and search bar border instead of native colors
Updated•18 years ago
|
Attachment #280992 -
Flags: approval1.9? → approval1.9+
| Assignee | ||
Updated•18 years ago
|
Keywords: checkin-needed
Comment 10•18 years ago
|
||
Checking in browser/themes/winstripe/browser/browser.css;
/cvsroot/mozilla/browser/themes/winstripe/browser/browser.css,v <-- browser.css
new revision: 1.95; previous revision: 1.94
done
Checking in browser/themes/winstripe/browser/searchbar.css;
/cvsroot/mozilla/browser/themes/winstripe/browser/searchbar.css,v <-- searchbar.css
new revision: 1.19; previous revision: 1.18
done
Checking in toolkit/themes/winstripe/global/autocomplete.css;
/cvsroot/mozilla/toolkit/themes/winstripe/global/autocomplete.css,v <-- autocomplete.css
new revision: 1.17; previous revision: 1.16
done
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: Firefox 3 → Firefox 3 M9
You need to log in
before you can comment on or make changes to this bug.
Description
•