Closed Bug 1162620 Opened 5 years ago Closed 5 years ago
Visited link on about:crashes isn't purple anymore
After bug 1161161, all the links (visited and not visited) are blue. Without color indication it's harder to know which crashes have been investigated/visited/submitted. I'm on Windows 7 (don't know if the problem happens on all platforms).
It happens on all platforms. :( This basically makes about:crashes useless for people who want to stay on top of the crashes they've encountered. Can we fix this, please?
This adds the the default color for visited links to crashes.xhtml.
Assignee: nobody → richard.marti
Status: NEW → ASSIGNED
Attachment #8602985 - Flags: review?(dao)
Comment on attachment 8602985 [details] [diff] [review] Bug1162620.patch I'm pretty sure this belongs in common.inc.css, and you don't want to use a platform color for this since the background color is hardcoded.
Attachment #8602985 - Flags: review?(dao) → review-
I wasn't sure if the other in-content pages also want the visited state but this should help the user to know what he already has seen. I'm using the default visited color from about:config, is this okay?
Comment on attachment 8603222 [details] [diff] [review] Bug1162620.patch :visited won't work for .text-link and .inline-link, since those aren't real links. r=me with these two lines removed
Attachment #8603222 - Flags: review?(dao) → review+
Fixed comment. Carrying over r+
Thanks for the quick fix!
I have seen this bug on Firefox nightly (20150507) on windows 8.1(32bit). Build ID 20150507030203 User Agent Mozilla/5.0 (Windows NT 6.3; rv:40.0) Gecko/20100101 Firefox/40.0 Latest Firefox beta & nightly showed blue color for uninvited link & purple color for visited link. Latest Firefox nightly: Build ID 20150721030212 User Agent Mozilla/5.0 (Windows NT 6.3; rv:42.0) Gecko/20100101 Firefox/42.0 Latest Firefox beta: Build ID 20150720220238 User Agent Mozilla/5.0 (Windows NT 6.3; rv:40.0) Gecko/20100101 Firefox/40.0 [bugday-20150722]
QA Whiteboard: [good first verify] → [good first verify][bugday-20150722]
You need to log in before you can comment on or make changes to this bug.