Active Link Annoyance...

[Pbartender]

I'm not certain if anyone else is seeing this... I hadn't noticed at home earlier today, but I'm seeing it now at work on IE 6.0 ...But...

It would seem that somewhere within the messageboard's stylesheet, there is something like an "a:active {font-variant: small-caps; font-weight: bold}" where it shouldn't be. Either that, or my browser isn't reading the styles the way it should.

In other words, for those of you .html/.css savvy, whenever I click on a link on the boards, the link turns to all bold capital letters for brief moment. Since the bolded capital take up more space than normal, that means all the other text in the line gets shifted over.

While it's not strictly detrimental to surfing the boards, it does get a little annoying after a while.

 

[Michael Morris]

This error came up when I added seperate CSS definitions for the top section and then switched over those definitions for the top banner. The goal is to get the header to look the same on every page here on ENWorld.

I think I know the cause, but I'm sorta tied up with the new Sci Fi site for the moment. However at some point today I do intend to address this - it's probably a matter of defining the default a:active call to font-variant: none;.

 

[Pbartender]

I took a quick peek through this thread's source file, and although you use a little different style format than I'm used to, I couldn't find any glaringly obvious problems (within my admittedly amateur web coding skills).

I'm curious... You've almost universally grouped a:hover with a:active (you do have it set for the default BODY tag, unless you were thinking of something else), but the problem only shows up for the a:active call.

Might this be a browser specific problem? In my personal experience, I've had problems with specific HTML tags using specific CSS properties in specific web-browsers... I've never been able to get BODY {background-color} to work in Netscape, for example. Are you looking at it from a different browser? Is anyone else seeing it, or not seeing it? I'll double-check it when I get home, just to make certain.

 

[Michael Morris]

I took a quick peek through this thread's source file, and although you use a little different style format than I'm used to, I couldn't find any glaringly obvious problems (within my admittedly amateur web coding skills).

I'm curious... You've almost universally grouped a:hover with a:active (you do have it set for the default BODY tag, unless you were thinking of something else), but the problem only shows up for the a:active call.

The body tag is the only one where I've forced VBulletin to seperate the two in an attempt to be rid of the problem with no success. It's odd.

Might this be a browser specific problem? In my personal experience, I've had problems with specific HTML tags using specific CSS properties in specific web-browsers...

Possibly, but Vbulletin does a pretty good job of custom building the pages to the browser's needs. It can even generate a page without a style sheet for very old browsers. Still, with all the different browsers out there who knows. It's definately a rendering glitch of some sort, but whether it's specific to IE I don't know and haven't checked.

I've never been able to get BODY {background-color} to work in Netscape, for example.

IE is more tolerant of non-standard tags than NS. To set the background color of any element in a stylesheet you use

[b]element[/b] {background: #FFFFFF;}

Where "element" is the item your setting (be it body, td, etc.) "background-color" will be accepted by IE but not NS or virtually any other browser. Coding specifically for IE can cause headaches because of this, but it's a feature (some gurus call it a bug) M$ refuses to remove because it makes other browsers look bad.

Are you looking at it from a different browser? Is anyone else seeing it, or not seeing it? I'll double-check it when I get home, just to make certain.

No, I'm seeing the problem you're describing and noted it immediately after adding the .banner and .announce elements to the style sheet. Push comes to shove, I can remove those custom elements in order to get rid of the glitch, but I'd rather find a work around because in the future I want to use a single php file to contain the heading banner for all the programs that might want to call it, (or at least all the styles) that way I don't have to update 17 odd styles to update one element.

For reference, I use IE 6.0 most of the time but test pages in NS 7.0 as well.

 

[Pbartender]

IE is more tolerant of non-standard tags than NS. To set the background color of any element in a stylesheet you use

[b]element[/b] {background: #FFFFFF;}

Where "element" is the item your setting (be it body, td, etc.) "background-color" will be accepted by IE but not NS or virtually any other browser. Coding specifically for IE can cause headaches because of this, but it's a feature (some gurus call it a bug) M$ refuses to remove because it makes other browsers look bad.

Hrm... I thought I'd tried that without success, but I might be mistaken. I'll have to try it again.

 

[Cthulhu's Librarian]

Possibly, but Vbulletin does a pretty good job of custom building the pages to the browser's needs. It can even generate a page without a style sheet for very old browsers. Still, with all the different browsers out there who knows. It's definately a rendering glitch of some sort, but whether it's specific to IE I don't know and haven't checked.o

It's not IE specific, I'm also seeing it in Mozilla Firebird 0.7

 

[Michael Morris]

It's not IE specific, I'm also seeing it in Mozilla Firebird 0.7

Ok guys, I'm on this now.

 

[Michael Morris]

The fix is as odd as the problem ::shrugs:: Anyway, it's gone now. Sorry for the inconvenience.

 

[Mark]

I knew you'd find it, Double-M! Bravo!