[WEB4LIB] Re: Cache problem? but where?

[D. Keith Higgs]

I have to agree with you Jeremy.  More and more browsers are becoming
sticklers for well formed HTML.  Failure to close a block element
(table, form, div, p, etc...) forces the browser to make certain very
unreliable assumtions about where to insert the appropriate closing tag.

If your not closing your block elements properly it doesn't matter which
browser your clients are using, you are at fault. If you are using a
WYSIWYG editor that commits this attrocity you should replace it
immediately.  If your editor, whatever it is does not properly close
paragraphs (<p>Yadda yadda.</p>) you should be shopping now for one that
does.
D. Keith Higgs <mailto:dkh2 at po.cwru.edu>
 Case Western Reserve University
  Webmaster - University Library
  Additional Information at http://www.cwru.edu/UL/

-----Original Message-----
From: web4lib at webjunction.org [mailto:web4lib at webjunction.org]
On Behalf Of Jeremy Foster
Sent: Monday, April 29, 2002 08:15 AM
To: Multiple recipients of list
Subject: [WEB4LIB] Re: Cache problem? but where?


I have not looked at the pages below..but a common problem with pages
not showing all content in Netscape 4.x is not closing table tags....

As a side note..why do they always say this is a Netscape problem? When
in reality it's a bad html programming practice not to close table tags.