Interviewed by CNN on 11/12/2012 16:58, Rick Merrill told the world: > For goodness sake: I though passing W3C compliance http://validator.w3.org/ > Was "standards mode"!
Not quite. The Validator checks if your code is acceptable under the rules of the version of HTML you declared in the heading. So, if you declared "transitional" mode, it will only check if your page fits "transitional." And, as far as I remember, all browsers render "transitional" pages in Quirks mode. The idea being that most transitional pages in the wild won't actually validate correctly, and even if they do, they are probably old pages composed in the olden days when it was standard practice to *rely* on a few misbehaviours of common browsers. The quirks mode simulates those old, well, quirks so old pages won't break horribly. > So which is really "better", > <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> > or > <!DOCTYPE html> ? Well, if you are building new pages using reasonably current practices, checking for valid codes and such, and more importantly if you want to use the new features of HTML5, then you should use the second one. The first one is probably best if you are just trying to bring old pages "up to code" so to speak -- aiming for HTML 4.01 Transitional lowers the bar quite a bit. HTML 4.01 Strict is becoming less useful nowadays that most browsers at least recognize the HTML5 header. Generally speaking, most HTML 4.01 Strict will validate as HTML5 too (except for the DTD, of course), but HTML5 gives your more flexibility (including adding back some elements that had been deprecated in 4.01). > Furthermore, Does SM's Composer do better with or assume one or the other? AFAIK, Composer has no support for HTML5 at all, and its compliance with HTML 4 is far from perfect. If you are using Composer, it's probably best to begin aiming for 4.01 transitional, and then, if you so desire, hand-tweak the code for 4.01 Strict or HTML5 compliance. -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from my private island. * Added by TagZilla 0.7a1 running on Seamonkey 2.14.1 * Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
