XHTML/CSS Redesign of Home Page

Thursday October 2nd, 2003

MozPhile writes: "In an effort to publicize a new CSS design for, a new mozdev project has been created. Based on the current design, this new one features valid XHTML 1.1 and CSS 2, with semantic HTML. First a fully standards-compliant browser, now a fully standards-compliant website to top it off!" Note that has not made any official statement regarding the design or whether they plan to use it.

#31 Re: Exactly - but do change the pictures

by jgraham

Thursday October 2nd, 2003 3:38 PM

You are replying to this message

> Do not use XHTML 1.1. (At all, ever. That's a general rule. Just don't do it.)

Well, that's a very general rule. What about times when you need to use application/xhtml+xml as the mime type for solid technical reasons? For example, try sending MathML over the wire as text/html and watch Mozilla choke on it. Coincidentally, this requires the html part of the content to be sent as XHTML 1.1 (at least, it does according to <…/valid-dtd-list.html#full> ) /In general/ sites should be written as html 4 unless they are prepared to put the effort in to make sure they are sending valid content. But if you are sure that your content is valid, then there is no reason not to send it as XHTML + correct mime type and, if you are using something that requires it, there's no reason not to use XHTML 1.1. Moreover, if you're clevel you can easilly send something as XHTML 1.1 to browsers that support it and dynamically change the content to be valid html 4 for browsers that don't support it - I believe <> does something similar using PHP - at the very least html 4 browsers don't get the xhtml shorttag form of empty elements i.e. the xhtml form has <img .... /> whilst the html form has <img ....>. If you've gone to all that trouble, dynamically switching the doctype also seems easy.