Menu
Community /Pin to ProfileBookmark
@NogDogAug 20.2005 — #
Not only the use of tables for visual presentation, but the use of deprecated tags and attributes. If using a HTML 4.01 Strict doctype, here are the errors that bit of code will produce:
Thus I was trying to point the original poster in the more up-to-date direction of using CSS for visual presentation instead of outdated techniques.@NogDogAug 21.2005 — #As long as you don't care how text-to-speach readers handle your page and don't plan on keeping the pages around long enough that they'll become truly obsolete and don't care how non-graphical browsers handle your web page, then by all means do whatever works most easily for you. And I don't mean that as a put-down: there are many sites where the above issues are not a serious problem. But if you ever get called on to create a site which [i]is[/i] standards compliant and as accessible as possible to all users and all media, it's good to take some time now to learn how to do it. I mean, if an old dog like me can learn CSS, all you young folks should have no problem. ?
Hopefully some day someone will come up with a WYSIWYG web authoring tool that is truly WYSIWYG [i]and[/i] able to create a page that is table-less (except for tabular data) and validates as [X]HTML Strict.
How do I center a table on a page?
If I decrease the size of a table (ie width=70%), how do I center it on the page?
Thanks, BJB ?
Sign in
to post a comment14 Comments(s) ↴
0
@NogDogAug 20.2005 — #Oh yeah. One draw back. Depending on what you're doing 70% will apply to the users screen resolution settings and will look different on an 800 x 600 vs 1024 x 768. If you want to keep it looking the same on different screen don't use % use pixels.
<div align="center">
<center>
<table border="0" cellpadding="0" cellspacing="0" style="border-collapse: collapse" width="400">
<tr>
<td width="100%"> </td>
</tr>
</table>
</center>
</div>
Of course the CSS people will have a whole other issue with using tables[/QUOTE]
Not only the use of tables for visual presentation, but the use of deprecated tags and attributes. If using a HTML 4.01 Strict doctype, here are the errors that bit of code will produce:
[list=1]
[*]Error Line 14 column 11: there is no attribute "ALIGN".
<div align="center">
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute.
[*] Error Line 15 column 7: element "CENTER" undefined.
<center>
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
[list]
[*] incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element), [*] by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead). [*] by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case.
[/list]
[*] Error Line 18 column 10: there is no attribute "WIDTH".
<td width="100%"> </td>
[/list]
[/quote]
Thus I was trying to point the original poster in the more up-to-date direction of using CSS for visual presentation instead of outdated techniques.
0
@NogDogAug 21.2005 — #As long as you don't care how text-to-speach readers handle your page and don't plan on keeping the pages around long enough that they'll become truly obsolete and don't care how non-graphical browsers handle your web page, then by all means do whatever works most easily for you. And I don't mean that as a put-down: there are many sites where the above issues are not a serious problem. But if you ever get called on to create a site which [i]is[/i] standards compliant and as accessible as possible to all users and all media, it's good to take some time now to learn how to do it. I mean, if an old dog like me can learn CSS, all you young folks should have no problem. ?Hopefully some day someone will come up with a WYSIWYG web authoring tool that is truly WYSIWYG [i]and[/i] able to create a page that is table-less (except for tabular data) and validates as [X]HTML Strict.