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

Jump to navigation Jump to search
Line 36: Line 36:
2. The next-best solution would be to persuade the W3C to include the autocomplete attribute in an XHTML module similar to the [http://www.w3.org/TR/xhtml-modularization/dtd_module_defs.html#a_module_Legacy Legacy module]. But I think that will never happen.
2. The next-best solution would be to persuade the W3C to include the autocomplete attribute in an XHTML module similar to the [http://www.w3.org/TR/xhtml-modularization/dtd_module_defs.html#a_module_Legacy Legacy module]. But I think that will never happen.


3. More plausibly, we could and browser support for a <code>formhistory</code> attribute in a vendor neutral URI such as <nowiki>http://www.legacymarkup.org/xmlns/formhistory</nowiki>, and implement it in a simple XHTML module. When converting content for serving as HTML, the XSL transformation to HTML would be trivial:
3. More plausibly, we could add browser support for a <code>formhistory</code> attribute in a vendor neutral URI such as <nowiki>http://www.legacymarkup.org/xmlns/formhistory</nowiki>, and implement it in a simple XHTML module. When converting content for serving as HTML, the XSL transformation to HTML would be trivial:


<blockquote><pre>
<blockquote><pre>
Line 58: Line 58:
and
and


<blockquote>
<blockquote><code>class="fh enable_form_history"</code></blockquote>
<code>class="fh enable_form_history"</code>
 
The two variations are necessary because an input might have autocomplete enabled within a form that generally wants autocomplete disabled (thanks to richmoore for pointing that out to me).
The two variations are necessary because an input might have autocomplete enabled within a form that generally wants autocomplete disabled (thanks to richmoore for pointing that out to me).


Navigation menu