• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

frontpage has tons of XHTML errors

But it is broke, so you're saying.. fix it? :eek:

anyhow I know what you mean; so it's not an important issue, I don't mind if it isn't fixed, but it's easily fixed using the tidy program which automatically formats it properly for you
 
Debug the page and send the results to Kyle, I'm sure he will appreciate your efforts.
 
Code:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
you will notice that the page isn't making an attempt to be xhtml but rather html 4.01 transitional. now granted there are still a shitload of errors, since you are pointint them out, you should especially make sure to use the correct terminology.

as a sidenote, i initially thought you were referring to microsoft frontpage (i was wondering why that would be in the forum help n feedback section), and i was going to reply no shit to that, but nevermind.
 
tim_m said:
Code:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
He means the forum's main page, not hardocp's front page (or at least I assume so, considering he linked the forum's main page). And it does indeed have an XHTML transitional doctype, but that's vB's problem I guess, not the [H]'s. And my guess is we would have tons of people complaining if any of these errors were actually hindering the users, but they're not. I'm a standards compliant kind of guy, but hey, it works. It'd be a pain in the ass to go through all the vB code to fix every little validation error.
 
I ran the main forum page thru a validator and got errors, most related to "nowrap" and "embed" tags as not being XHTML compliant. Then I ran vBulletin's own main forum page and it passed with flying colors.

So it looks to me like the issue has to do with how the banner ads have been inserted using html 4.01 transitional code in what is declared by default (vBulletin) as an XHTML doc type. But they work just fine and don't seem to be a problem.

I honestly can't see how it'd be of any benefit to alter the code to "fix" what amounts to a non-problem here.
 
Lethal said:
I ran the main forum page thru a validator and got errors, most related to "nowrap" and "embed" tags as not being XHTML compliant. Then I ran vBulletin's own main forum page and it passed with flying colors.

So it looks to me like the issue has to do with how the banner ads have been inserted using html 4.01 transitional code in what is declared by default (vBulletin) as an XHTML doc type. But they work just fine and don't seem to be a problem.

I honestly can't see how it'd be of any benefit to alter the code to "fix" what amounts to a non-problem here.

If you go and try to fix something, it will get way more borked than fixing its worth- Gulliver's Philosophy
 
Lethal said:
I ran the main forum page thru a validator and got errors, most related to "nowrap" and "embed" tags as not being XHTML compliant. Then I ran vBulletin's own main forum page and it passed with flying colors.

So it looks to me like the issue has to do with how the banner ads have been inserted using html 4.01 transitional code in what is declared by default (vBulletin) as an XHTML doc type. But they work just fine and don't seem to be a problem.

I honestly can't see how it'd be of any benefit to alter the code to "fix" what amounts to a non-problem here.
Lethal shows off that big brain one more time...
 
Back
Top