bug found

[sr71000]

in the active/recent discussions box there's a little bug. Visited links on hover have black font. They also have a black background. Bug found in firefox 2.0.0.6

[RobRich]

Works fine for my Firefox install, though I verified against the latest nightly build of Minefield 3.0a8pre. I will check Firefox 2.x when I get back home, as I am actually riding in a car heading towards Orlando right now.

[Atomic Rooster]

I've noticed that bug too now that you mention it. But it's not consistent. Some visited links for me are a black background with white font, while others are just a black background with no visible font. I'm also using FF version 2.0.0.6.

[sr71000]

In your css files here's your problem

A.top2:hover
{
font-family: Verdana, Arial;
white: white;****************************
font-size: 8pt;
font-weight: bold;
text-decoration: none;
background: #00283C
}

that should say color: white yay i'm a super nerd!!

[sr71000]

hehe...so i'm an idiot...i realized i found the problem before but my fix was wrong. in the embeded css firefox gives precendence to order listed so because a:visited comes after a:hover in the css, when a visited link is hovered over in firefox, the visited settings still get priority! In the css, you have to put a:visited then a:hover so that a:hover setting will override the a:visited settings when it's hovered. Yay for firefox!

[Atomic Rooster]

OK. Thats all well and good, but how does one do all this? I'm not familiar with all this Firefox CSS stuff.

[sr71000]

that's something robs gotta fix in the code. I have the web developers plugin in firefox so i can mess with the stuff on the fly, but rob's gotta fix it for good in the code!

[RobRich]

Actually, that would be for Scott to edit. I can change some CSS parameters through vB style management, but apparently not the order the code contained within the CSS file. I do not have file level access to the required directory.

[sr71000]

lol. ok. I found the problem and fixed it (with some stuff i have to edit css on the fly) so if scott feels like being lazy have him pm me or something and i can point him in the right direction!

[sr71000]

hey rob. did you or are you going to let scott know or should i message him myself? Just wondering as I haven't seen anything about this in a little bit!

[RobRich]

I dropped Scott a line. He is a busy man with a tight schedule, so don't expect overnight results on a low-priority bug.

[sr71000]

just checking!

[kenboyles72]

what css property did you change?

[sr71000]

in the inline css for the page, you have to switch the order in which a.top:visited and a.top:hover appear. They should be in the order I listed them. They are given priority starting from the bottom. So in the code a.top:hover comes first and has background color and font color set (black/white) then comes a.top:visited which has just the font color set (black). When both conditions are true (visited and hover) you start at the top and hit hover first...the settings for the text are black background white text. Then we continue through the styles and hit a.top:visited where the text color is overridden and turned black! black on black makes it impossible to read. does that make sense now?