Originally posted by: Woosta
Originally posted by: GodlessAstronomer
Originally posted by: Woosta
Q: Does it bother me that people think they're using XHTML across the HTTP protocol when the Content-Type served is text/html, and the document at hand contains markup errors, along with the use of table elements for layout?
A: Yes
Serving a page with a content type of XHTML is possibly the stupidest thing you could do at this point in time. Web software just isn't mature enough, you're almost guaranteeing that your website will be rendered useless by some user-generated content.
Exactly, which is why I stick with HTML 4.01 Strict![]()
Originally posted by: GodlessAstronomer
Originally posted by: Woosta
Originally posted by: GodlessAstronomer
Originally posted by: Woosta
Q: Does it bother me that people think they're using XHTML across the HTTP protocol when the Content-Type served is text/html, and the document at hand contains markup errors, along with the use of table elements for layout?
A: Yes
Serving a page with a content type of XHTML is possibly the stupidest thing you could do at this point in time. Web software just isn't mature enough, you're almost guaranteeing that your website will be rendered useless by some user-generated content.
Exactly, which is why I stick with HTML 4.01 Strict![]()
Although it's not as risky, there's still not a really compelling reason to go strict. If you're interested, Jeff Atwood had a really interesting blog post about this just a day or two ago. Here.
Originally posted by: Descartes
blah blah blah
Listen techie code monkeys, just make it work to my specs, that's all I care about.Originally posted by: Woosta
blah blah blah