Archive —

"Mind you, the Null Packet is not created by compressing a packet until it disappears into nothingness. Such a compression scheme might not be reversible."

June 15, 2004

I feel like debunking two myths that roam around the two IRC channels I hang around in (#html on and #web on, namely...

  1. ...that <table> was never meant endorsed by a spec to lay out web pages, and...
  2. ...that XHTML MUST NOT be sent as text/html.

A lot of people will scream these things at you, but apparently they haven't read the relevant specs thoroughly enough. I quote the HTML 3.2 table section:

"HTML 3.2 includes a widely deployed subset of the specification given in RFC 1942 and can be used to markup tabular material or for layout purposes. Note that the latter role typically causes problems when rend[er]ing to speech or to text only user agents."


Now, of course you shouldn't misuse <table> for layout purposes, but claiming that they were never intended to do layout is a lie.

And then we have the people who claim that XHTML MUST NOT be sent as text/html. Debunking that myth is also just a matter of referring to the relevant spec. The summary clearly states that XHTML SHOULD NOT be sent as text/html, and SHOULD NOT is clearly defined in RFC2119 (there's probably an RFC on how to properly sort your laundry) as:

"This phrase, or the phrase 'NOT RECOMMENDED' mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label."


I'd say that Internet Explorer not being able to even display XHTML sent with the proper MIME type is a valid reason for implementing aforementioned behavior. At least, that's my reason.

Next time you want to complain about something, do your homework.

<< | Previous entry (June 12, 2004) | Next entry (June 16, 2004) | >>
Back to Archive