317432 - Visited and unvisited link colors on buglist.cgi are too similar

Status: RESOLVED WORKSFORME

(Bugzilla :: Query/Bug List, defect)

Description

[:Gavin Sharp [email: [e-mail]]]

When browsing a buglist, I like to be able to identify visited bugs, and the new stylesheet changes (bug 250400) made this a lot harder since it made the :visited and :link colors are too similar. Maybe it has to do with the alternating row backgrounds, but I find that with long bug lists the link colors "blend in" together too easily. I'll see if I can come up with something better that doesn't look ugly :).

Comment 1

[Dave Miller [:justdave]]

I don't plan to work on these at this point because the broader focus is now on trying to upgrade to Bugzilla 2.22, and it'll all have to be redone anyway to fit the 2.22 templates.  But if someone else wants to show me what to patch on any of these I'll be happy to patch the current install between now and then.

Comment 2

[Reed Loden [:reed]]

Is this still an issue?

Comment 3

[Wayne Mery (:wsmwk)]

I agree - too similar.  Blue vs light purple isn't enough difference
(I thought it was just me)

Comment 4

[Frédéric Buclin]

You can overwrite the color of links from your browser, if the contrast isn't high enough. Colors we use are pretty standard.

Comment 5

[Wayne Mery (:wsmwk)]

I changed browser.visited_color to red and didn't see a difference.

Comment 6

[:Gavin Sharp [email: [e-mail]]]

Yes, I think this is still an issue. I still find bug lists harder to read than they used to be, and others have made the same comments. Overriding link colors on the client side shouldn't be necessary - there's no reason not to make to fix this once someone proposes a better color palette. I haven't really taken the time to "come up with something better", but darkening the "visited" color and/or slightly brightening the normal link color would probably be a good start.

Comment 7

[Gervase Markham [:gerv]]

b.m.o. does not change the colours from the default; moving bug upstream.

Gerv

Comment 8

[Max Kanat-Alexander]

We fixed this, I believe it was in 3.6 or 4.0.