3 ms·
No browser ever paid any attention to the version of the HTML specified. The only use for DOCTYPE—and the reason it remains in HTML5—is "doctype switching", i.e
by rimantas 12y ago
No browser ever paid any attention to the version of the HTML specified. The only use for DOCTYPE—and the reason it remains in HTML5—is "doctype switching", i.e. different rendering modes are triggered in the browsers. You can use "html", "html5", "html6.2" or "foobarbaz" as your doctype, the effect will be the same—they will all trigger standards compliant mode.
- pbhjpbhj 12y ago>'You can use "html", "html5", "html6.2" or "foobarbaz" as your doctype, the effect will be the same—they will all trigger standards compliant mode.' // You're wrong if your asserting that any doctype produces the same results globally but it probably doesn't matter unless you're targeting legacy UA. See e.g. "Appendix: Handling of Some Doctypes in text/html" at https://hsivonen.fi/doctype/ https://hsivonen.fi/doctype/ or Eric Meyer's http://archive.oreilly.com/pub/a/network/2000/04/14/doctype/index.html http://archive.oreilly.com/pub/a/network/2000/04/14/doctype/... (for MacIE5 ... like I said it probably won't matter!).
- gsnedders 12y agoSpeaking of IE/Mac, that's the reason why the HTML DOCTYPE now is `<!doctype html>`. If it hadn't been for IE/Mac, it'd be `<!doctype>`.
- kibibu 12y agoI have vague memories of Frames not working under the HTML4 Strict doctype
- scriptproof 12y agoMaybe but if you use real DOCTYPE such as <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> http://www.w3.org/TR/html4/strict.dtd"> then you will see huge difference in rendering.