I hate to say it but you have a big task ahead if you are going to try and make all the output validate.
I'll venture to say it can be done, but unless Paul decides W3C validatation is a top priority and re-writes a lot of things, you'll wind up with a rather customized script and template arrangement that will only last until your next upgrade.
I'm a W3C validation fan myself and do ensure what HTML I hand write all validates but with dynamic content and scripts it's usually a loosing battle to worry a great deal about 3rd party HTML obsessivly. Best to make a quick decision if the script provides enough value to put aside W3C or accessability concerns, if possible... or use something like webmastersite.net 'Pro' scripts which are able to be modified for your own use.
I have a site which I can virtually eliminate most all 3rd party scripts "as is" since it must maintain Section 508 accessability standards. At least with a licensed WSN Links it's flexable and easy enough to modify for rigid requirements.
I'm using the default templates with WSN Links myself. Is your site looking messed up with them? I've not noticed anything strange looking in 3 different browsers -- IE5, Opera 8 and Firefox.
Actually the output of WSN has validated by default when checked since 2.40, it simply hasn't been checked for a while since I'd presumed someone would've mentioned any issues. It looks like there are a few small validation issues, should be cleaned up in 3.3.6.
The <tr>s anyhow are controlled by your selection of columns in your settings. The lack of them is not a validation issue, it's a necessity to allow a flexible number of columns. If you specify the <tr> in the template you're forcing it to one column, and causing errors due to trying to duplicate something the script already handles.
the code I've pasted in the first post is the view source from the browser output, not a cut n paste from the default template. Therefore you will see that the HTML doesn't make much sense and screws up my layout......
Comments on why is the HTML not correct in
Forum Regular
Usergroup: Customer
Joined: Aug 05, 2005
Total Topics: 94
Total Comments: 272
this is from the default template.... why is the HTML not correct..?
there's no opening <TR>
there's only one <TD> and it seems to have a 49% width...?
at the end there's an opening <TR>...
I'm sure there's a reason, but I'm having problems with the layout.....
Forum Regular
Usergroup: Customer
Joined: Jan 11, 2006
Total Topics: 48
Total Comments: 166
I hate to say it but you have a big task ahead if you are going to try and make all the output validate.
I'll venture to say it can be done, but unless Paul decides W3C validatation is a top priority and re-writes a lot of things, you'll wind up with a rather customized script and template arrangement that will only last until your next upgrade.
I'm a W3C validation fan myself and do ensure what HTML I hand write all validates but with dynamic content and scripts it's usually a loosing battle to worry a great deal about 3rd party HTML obsessivly. Best to make a quick decision if the script provides enough value to put aside W3C or accessability concerns, if possible... or use something like webmastersite.net 'Pro' scripts which are able to be modified for your own use.
I have a site which I can virtually eliminate most all 3rd party scripts "as is" since it must maintain Section 508 accessability standards. At least with a licensed WSN Links it's flexable and easy enough to modify for rigid requirements.
I'm using the default templates with WSN Links myself. Is your site looking messed up with them? I've not noticed anything strange looking in 3 different browsers -- IE5, Opera 8 and Firefox.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Actually the output of WSN has validated by default when checked since 2.40, it simply hasn't been checked for a while since I'd presumed someone would've mentioned any issues. It looks like there are a few small validation issues, should be cleaned up in 3.3.6.
The <tr>s anyhow are controlled by your selection of columns in your settings. The lack of them is not a validation issue, it's a necessity to allow a flexible number of columns. If you specify the <tr> in the template you're forcing it to one column, and causing errors due to trying to duplicate something the script already handles.
Forum Regular
Usergroup: Customer
Joined: Aug 05, 2005
Total Topics: 94
Total Comments: 272
the code I've pasted in the first post is the view source from the browser output, not a cut n paste from the default template. Therefore you will see that the HTML doesn't make much sense and screws up my layout......
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Every page of 3.3.6 I can find validates as html 4.01 transitional according to the w3c's validator.