55
edits
m (→The Problem) |
|||
Line 34: | Line 34: | ||
* [http://www.benjaminhawkeslewis.com/legacymarkup/dtd/iso-html-15445-2000-plus-autocomplete.dtd ISO/IEC 15445:2000 HTML plus autocomplete] | * [http://www.benjaminhawkeslewis.com/legacymarkup/dtd/iso-html-15445-2000-plus-autocomplete.dtd ISO/IEC 15445:2000 HTML plus autocomplete] | ||
I've | To use such as custom doctype, simply declare it like so: | ||
<!DOCTYPE html SYSTEM "http://www.benjaminhawkeslewis.com/legacymarkup/dtd/html-4.01-strict-plus-autocomplete.dtd"> | |||
Contrary to common misapprehensions, declaring a custom DTD in this way does '''not''' trigger Quirks mode. (Except perhaps in IE 5/Mac -- can anyone confirm that?) Unrecognized doctypes with a URI are interpreted in full Standards mode. See: | |||
* [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnie60/html/cssenhancements.asp#cssenhancements_topic2 MSDN: CSS Enhancements in Internet Explorer 6] | |||
* [http://www.opera.com/docs/specs/doctype/ The Opera 9 DOCTYPE Switches] | |||
* [http://developer.apple.com/internet/bestwebdev.html Apple Developer Connection: Web Development Best Practices] | |||
* [http://developer.mozilla.org/en/docs/Mozilla's_DOCTYPE_sniffing Mozilla Developer Center: Mozilla's DOCTYPE Switching] | |||
I've added an [http://www.benjaminhawkeslewis.com/legacymarkup/examples/html-4.01-strict-plus-autocomplete.html example document using the Strict version] to my site. | |||
4. The X in XHTML stands for "extensible". But because all elements and attributes are namespaced in XML and the W3C jealously guard their XHTML namespace from extension by others, a site author may not do the same with XHTML-based markup. While it is certainly possible to build a custom XML DTD to include an <code>autocomplete</code>, the act would be meaningless as the W3C have made it clear they would not regard documents extending the XHTML namespace in this way as even using XHTML at all ([http://www.w3.org/TR/xhtml-modularization/conformance.html#s_conform XHTML Modularization 1.1: Working Draft: Conformance Definition], also see [http://alistapart.com/articles/customdtds2/ A List Apart: More About Custom DTDs]). | 4. The X in XHTML stands for "extensible". But because all elements and attributes are namespaced in XML and the W3C jealously guard their XHTML namespace from extension by others, a site author may not do the same with XHTML-based markup. While it is certainly possible to build a custom XML DTD to include an <code>autocomplete</code>, the act would be meaningless as the W3C have made it clear they would not regard documents extending the XHTML namespace in this way as even using XHTML at all ([http://www.w3.org/TR/xhtml-modularization/conformance.html#s_conform XHTML Modularization 1.1: Working Draft: Conformance Definition], also see [http://alistapart.com/articles/customdtds2/ A List Apart: More About Custom DTDs]). |
edits