Closed
Bug 437456
Opened 16 years ago
Closed 16 years ago
Theme for Mac shows unreadable color scheme in bookmarks dialog (black text on dark background)
Categories
(Firefox :: Theme, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: stesch, Unassigned)
References
()
Details
(Keywords: access)
Attachments
(1 file)
44.34 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; de; rv:1.9) Gecko/2008053008 Firefox/3.0 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; de; rv:1.9) Gecko/2008053008 Firefox/3.0 When you add a bookmark and choose a folder, the folder listing is barely readable. The folder names are black and the background very dark gray. Reproducible: Always
Reporter | ||
Comment 1•16 years ago
|
||
On 10.5 the folder names are white and perfectly readable. On 10.4 it is black on gray, very bad. Since the FF3 "Final" is expected for June 17 it is safe to assume that this bug will stay.
Reporter | ||
Updated•16 years ago
|
Severity: normal → major
Version: unspecified → 3.0 Branch
Comment 3•16 years ago
|
||
They are also black and almost unreadable on my 10.5.
Reporter | ||
Comment 4•16 years ago
|
||
I tried another theme (hard to find these days ...) and the bookmark dialog is readable. Had to switch back to the default one. So it's really "just" something in the default FF3 theme for Mac.
Updated•16 years ago
|
Reporter | ||
Comment 6•16 years ago
|
||
(In reply to comment #4) > I tried another theme (hard to find these days ...) and the bookmark dialog is > readable. Had to switch back to the default one. The theme I tried was "Aero Silver Fox Basic 3.0.1". Just to see if it's a common problem or could be solved with changes to the theme.
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9) Gecko/2008061004 Firefox/3.0 Confirmed on 10.5
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Theme for Mac shows unreadable color scheme in bookmarks dialog → Theme for Mac shows unreadable color scheme in bookmarks dialog (black text on dark background)
Comment 11•16 years ago
|
||
The problem appears to be in the profile. If I use Firefox from an account which has never used it before, or if I create a new profile, then that instance has dialog text of white characters. I use (and only have) the default theme, though at one time I may have had another theme(s) installed and active.
Comment 12•16 years ago
|
||
For me, it appears that the Live HTTP Headers extension (<http://livehttpheaders.mozdev.org/>) is causing the problem. Disabling the extension (and restarting) was enough to fix the problem. I'll be reporting a bug to the extension author.
Reporter | ||
Comment 13•16 years ago
|
||
(In reply to comment #12) > For me, it appears that the Live HTTP Headers extension > (<http://livehttpheaders.mozdev.org/>) is causing the problem. Disabling the > extension (and restarting) was enough to fix the problem. > > I'll be reporting a bug to the extension author. The text is white on dark gray when I disable this extension. BUT: I don't have this problem on Windows XP or with another theme.
Comment 14•16 years ago
|
||
Thanks, Phil! Did you contact the author yet? I'm marking this bug as invalid for now since it is an extension issue.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 15•16 years ago
|
||
(In reply to comment #14) > Thanks, Phil! Did you contact the author yet? I'm marking this bug as invalid > for now since it is an extension issue. > Haven't you read comment #13? This is a problem in the theme, because other themes (on Mac or the default theme on Windows) don't have this problem. You can't expect authors of extensions to check on all available systems. BTW: At the moment only two users confirmed that this is related to Live HTTP Headers. There could be more extensions affected.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Comment 16•16 years ago
|
||
Marking bug as incomplete. A repro has been identified with the liveHTTPHeaders extension, and disabling it will not show the problem. Leaving it to the extension author to identify the problem. Feel free to reopen once we have more information on a fix for the extension, or if its related to the Mac theme.
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → INCOMPLETE
Reporter | ||
Comment 17•16 years ago
|
||
(In reply to comment #16) > Marking bug as incomplete. A repro has been identified with the > liveHTTPHeaders extension, and disabling it will not show the problem. > > Leaving it to the extension author to identify the problem. Feel free to > reopen once we have more information on a fix for the extension, or if its > related to the Mac theme. What information is missing?
Comment 18•16 years ago
|
||
Stefan, he means that until more info is found by the author of the extension regarding this problem (whether this is an issue with the Mac theme or not), this is marked as incomplete. Basically, we want to wait for the authors input once he figures out the problem.
Comment 19•16 years ago
|
||
(In reply to comment #14) > Thanks, Phil! Did you contact the author yet? I found an existing bug for the extension, to which I added a comment referring back to this bug. The Mozdev bug is <https://www.mozdev.org/bugs/show_bug.cgi?id=19145>.
Comment 20•16 years ago
|
||
Okay, so the extension does stupid things: chrome.manifest: overlay chrome://browser/content/browser.xul chrome://livehttpheaders/content/TasksOverlay.xul ... TasksOverlay.xul: <?xml version="1.0"?> <?xml-stylesheet type="text/css" href="chrome://livehttpheaders/skin/livehttpheaders.css"?> ... livehttpheaders.css: /* Set text color for the whole tree - just to be safe */ treechildren { color: #000000; }
Comment 21•16 years ago
|
||
> livehttpheaders.css:
> /* Set text color for the whole tree - just to be safe */
> treechildren {
> color: #000000;
> }
haha. thanks for looking dao.
Group: mozillaorgconfidential
Updated•16 years ago
|
Status: RESOLVED → VERIFIED
Updated•16 years ago
|
Group: mozillaorgconfidential
You need to log in
before you can comment on or make changes to this bug.
Description
•