Open
Bug 524337
Opened 16 years ago
Updated 11 years ago
Outline around location bar disappears on https sites
Categories
(SeaMonkey :: Themes, defect)
SeaMonkey
Themes
Tracking
(Not tracked)
NEW
People
(Reporter: beanboy, Unassigned)
References
()
Details
(Keywords: classic, Whiteboard: [seamonkey-2.0-affected])
Attachments
(1 file)
|
83.26 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0
The outline around the location bar that is normally present on standard http sites disappears on https sites.
Reproducible: Always
Steps to Reproduce:
1. Observe location bar on an http site.
2. Visit an https site.
3. Observe that the outline around the location bar has disappeared.
Actual Results:
The outline around the location bar has disappeared.
Expected Results:
The outline around the location bar is still present.
| Reporter | ||
Comment 1•16 years ago
|
||
Based on my tests, this issue is not present in XP. It seems like it might only
be present in Vista (and quite possibly Windows 7).
Comment 5•15 years ago
|
||
This will only happen in the classic theme not sure why but something to investigate.
Updated•15 years ago
|
Version: unspecified → SeaMonkey 2.0 Branch
Comment 7•15 years ago
|
||
not that i know of
Comment 11•12 years ago
|
||
This bug is still around in 2.13.2. In bug 710455, comment 2, Philip Chee mentioned that this is a bug in the Mozilla Widget code. Is this a broader bug that has its own bug ID, or is it all confined to what's reported in this bug?
Comment 12•12 years ago
|
||
Someone going to work on this I was waiting for like a year now for this to be fixed
Comment 13•12 years ago
|
||
(In reply to Steve Lis from comment #2)
> Based on my tests, this issue is not present in XP. It seems like it might
> only
> be present in Vista (and quite possibly Windows 7).
It's in Windows Vista,7, & 8
The coding didn't change a lot since vista
Comment 14•12 years ago
|
||
Basically our problem is that native themeing overrides the background colour, so we can't set the colour on the URLbar itself. (In fact Linux makes it worse because the native theming is on a different element in Linux autocomplete.) What we do instead is to set the background colour on the content of the autocomplete element. However this means that we're bound by the area that the native theme code says is the content. Linux claims that the border is 3px wide, which is why the screenshot in bug 869965 shows a bit of padding between the border and the background. On the other hand, Windows Vista and later claims that the border is 0px wide, which is why the screenshot in bug 524337 shows the background completely obscuring the border.
Comment 16•12 years ago
|
||
Duplicate bug 869965 is on Linux trunk. Also, comment #5 deserves a keyword. And finally, this is a styling bug, it doesn't correspond to the description of the "Location Bar" component, which is described as follows:
«This is the type-in history for the Location bar in the browser window. This includes behavior of the autocomplete widget for URIs, as well as the storage and expiration of the entries. Examples of appropriate bugs: URIs incorrectly added to the drop down list, crashes, hangs, slowness when using this feature.»
I'm changing the bug header accordingly.
Component: Location Bar → Themes
Keywords: classic
OS: Windows Vista → All
Hardware: x86 → All
Whiteboard: [seamonkey-2.0-affected]
Version: SeaMonkey 2.0 Branch → Trunk
Comment 17•12 years ago
|
||
I see this as well on Linux with the default KDE4 desktop theme and SeaMonkey's "classic" theme, hence indeed a cross-platform issue.
Interestingly, when switching to a different desktop theme it may happen that the colorization of the location bar is actually incomplete (see bug 354940 attachment 825525 [details] for a screenshot). Thus, the covered area may be either too large or too small, depending on the underlying theme's properties.
You need to log in
before you can comment on or make changes to this bug.
Description
•