Erm, FWIW, tags like B and CENTER are supposed to have closure to them, being a character-level and block-level tag, respectively. OTTOMH, the only tags in HTML that are not closed are HR and BR; P is considered to be ok to leave unclosed because of backwards compability with about 99% of the pages out there, but with some CSS browsers, P needs to be explicitly closed. Most browsers are smart enough to realize that a character-level tag like B or EM should close at the start of the next block-level tag, and that for non-container block-level tags (P, PRE, BLOCKQUOTE, as opposed to container tags like TABLE, UL, or LI), they should close at the start of the next block-level tag, but this is not a good assumption to make with browsers particularly when CSS is involved.
I'm not sure how that will affect your code, but I did want to point out that misunderstanding in your code header.
Dr. Michael K. Neylon - mneylon-pm@masemware.com
||
"You've left the lens cap of your mind on again, Pinky" - The Brain
| [reply] |
xhtml can't
handle the unclosed <p> tag the way HTML could.
If you are sticking with HTML 4.0 most CSS browsers who
dislike the assumed closure of the P tag can be spoofed with
the very evil xmlish <p/> but please don't tell
anyone _I_ told you that. =)
As xhtml becomes more prevalent, lightweight checkers
will become more popular and handy.
--
$you = new YOU;
honk() if $you->love(perl)
| [reply] |
Erm, it won't affect the code in the slightest.
You are absolutely correct - tags like <b> and <center> are supposed to have closure. On the (not so) odd occasion that they don't, however, the performance of the script will not be affected. Should the code have been intended to validate HTML then you might have a point.
I'm not sure how that will affect your attention to detail, but I did want to point out the misunderstanding in your interpretation of the code header.
| [reply] |