The autocomplete attribute and web documents using XHTML: Difference between revisions

Jump to navigation Jump to search
m
Line 6: Line 6:
However, there is currently no way to trigger the same user agent functionality with an attribute in XHTML. This constitutes an unnecessary obstacle to the adoption of XML-based markup.
However, there is currently no way to trigger the same user agent functionality with an attribute in XHTML. This constitutes an unnecessary obstacle to the adoption of XML-based markup.


By adopting my solution and supporting a small XHTML module and delimited <code>class</code> microformat, browsers could enable authors serving XHTML 1.0 as text/html to trigger the same behaviour with <code>class="fh disable_form_history"</code> ([http://www.benjaminhawkeslewis.com/legacymarkup/examples/xhtml-1.0-strict-plus-autocomplete-html-compatible.html example XHTML 1.0 document]) and authors serving XHTML properly as application/xhtml+xml to trigger the same behaviour with a namespaced attribute (<code>fh:form_history="off"</code>) ([http://www.benjaminhawkeslewis.com/legacymarkup/examples/xhtml-1.1-plus-formhistory-with-dtd-draft1.xhtml example modularized XHTML document]). Those authors who wish to serve both XHTML and HTML properly using an XSL transformation would could convert to the HTML <code>autocomplete</code> attribute with simple XSL rules.
If the W3C adopts Web Forms 2.0 then this problem will be solved.
 
If that doesn't happen, by adopting my solution and supporting a small XHTML module and delimited <code>class</code> microformat, browsers could enable authors serving XHTML 1.0 as text/html to trigger the same behaviour with <code>class="fh disable_form_history"</code> ([http://www.benjaminhawkeslewis.com/legacymarkup/examples/xhtml-1.0-strict-plus-autocomplete-html-compatible.html example XHTML 1.0 document]) and authors serving XHTML properly as application/xhtml+xml to trigger the same behaviour with a namespaced attribute (<code>fh:form_history="off"</code>) ([http://www.benjaminhawkeslewis.com/legacymarkup/examples/xhtml-1.1-plus-formhistory-with-dtd-draft1.xhtml example modularized XHTML document]). Those authors who wish to serve both XHTML and HTML properly using an XSL transformation would could convert to the HTML <code>autocomplete</code> attribute with simple XSL rules.


== Background ==
== Background ==

Navigation menu