I finally got tired of the new bugzilla color scheme making it impossible to
tell visited and unvisited links apart, but the following in
userContent.css helped:
@-moz-document
url-prefix(https://bugzilla.mozilla.org/buglist.cgi),
url-prefix(https://bugzilla.mozilla.org/show_bug.cgi)
{
:link { color: #0000EE !important }
:visited { color: #551A8B !important }
:link:active, :visited:active { color: #EE0000 ! important }
}
Posted by bzbarsky at November 28, 2005 6:31 PM
You should try out my Stylish extension (http://forums.mozillazine.org/viewtopic.php?t=327735) to manage your user styles.
Posted by: Jason Barnabe on November 28, 2005 7:45 PMThat extension doesn't work with Seamonkey, so it's pretty useless to me...
Posted by: Boris on November 28, 2005 8:07 PMI'm curious if there's a reason why you used two url-prefix selectors rather than one domain one. Are there performance differences or anything, or is this simply a case of "first way to do it which came to mind"?
Posted by: Sander on November 29, 2005 7:21 AMSander, Boris' rules doesn't match testcases uploaded in Bugzilla.
Posted by: Adam Hauner on November 29, 2005 10:09 AMI've seen some really scary sites that use center/font/th/broken tables/scripts and replace all the semantics with CSS classes. Making changes to that with user CSS can be a complete nightmare.
Before 1.5 and the URL selectors, my usercontent.css was so complex with this stuff I had to use multiple files. Most of it consisted of things like "html>#page>.class>br~font+center:last-child".
Sander, Adam is right. I didn't want to screw up attachments.
Posted by: Boris on November 29, 2005 11:41 AMHave you filed a bug on Bugzilla about getting the theme changed? I agree this sucks, and I'd be happy to fix it.
Posted by: Gerv on November 30, 2005 12:48 PMGerv, there is an existing bug (filed by Gavin, as I recall). But no, I didn't file a bug -- my experiences with filing bugs on bugzilla and LXR about the functionality regressions they've had due to "security fixes" have been pretty discouraging; it really just wasn't worth my time filing bugs, arguing about it, and then _still_ having the original problem when I could fix this locally as here.
All I need to do now is set up decent local tree indexing and I can also start ignoring further LXR breakage...
Posted by: Boris on November 30, 2005 1:35 PM