[html5] r6413 - [c] (0) Semi-allow <input type=number maxlength> for legacy reasons. Fixing http [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2011-08-10 16:54:57 -0700 (Wed, 10 Aug 2011)
New Revision: 6413

Modified:
   complete.html
   index
   source
Log:
[c] (0) Semi-allow <input type=number maxlength> for legacy reasons.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=12781

Modified: complete.html
===================================================================
--- complete.html	2011-08-10 22:56:55 UTC (rev 6412)
+++ complete.html	2011-08-10 23:54:57 UTC (rev 6413)
@@ -95564,6 +95564,13 @@
   way to specify possible targets for fragment identifiers in <a href=#url title=URL>URLs</a>. The <code title=attr-id><a href=#the-id-attribute>id</a></code>
   attribute should be used instead.</p>
 
+  <!-- remove this once type=number is widely supported -->
+  <p>Authors should not specify the <code title=attr-input-maxlength><a href=#attr-input-maxlength>maxlength</a></code> attribute on
+  <code><a href=#the-input-element>input</a></code> elements whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#number-state title=attr-input-type-number>Number</a> state. One valid reason
+  for using the attribute regardless is to help legacy user agents
+  that do not support <code><a href=#the-input-element>input</a></code> elements with <code title="">type="number"</code> to still render the text field with a
+  useful width.</p>
+
   <p class=note>In <a href=#syntax>the HTML syntax</a>, specifying a <a href=#syntax-doctype title=syntax-DOCTYPE>DOCTYPE</a> that is an <a href=#obsolete-permitted-doctype>obsolete
   permitted DOCTYPE</a> will also trigger a warning.</p>
 
@@ -95601,6 +95608,9 @@
    attribute on an <code><a href=#the-a-element>a</a></code> element, if its value is not the
    empty string.</li>
 
+   <li><p>The presence of a <code title=attr-input-maxlength><a href=#attr-input-maxlength>maxlength</a></code> attribute on
+   an <code><a href=#the-input-element>input</a></code> element whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#number-state title=attr-input-type-number>Number</a> state.</li>
+
   </ul><p>Conformance checkers must distinguish between pages that have no
   conformance errors and have none of these obsolete features, and
   pages that have no conformance errors but do have some of these

Modified: index
===================================================================
--- index	2011-08-10 22:56:55 UTC (rev 6412)
+++ index	2011-08-10 23:54:57 UTC (rev 6413)
@@ -91011,6 +91011,13 @@
   way to specify possible targets for fragment identifiers in <a href=#url title=URL>URLs</a>. The <code title=attr-id><a href=#the-id-attribute>id</a></code>
   attribute should be used instead.</p>
 
+  <!-- remove this once type=number is widely supported -->
+  <p>Authors should not specify the <code title=attr-input-maxlength><a href=#attr-input-maxlength>maxlength</a></code> attribute on
+  <code><a href=#the-input-element>input</a></code> elements whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#number-state title=attr-input-type-number>Number</a> state. One valid reason
+  for using the attribute regardless is to help legacy user agents
+  that do not support <code><a href=#the-input-element>input</a></code> elements with <code title="">type="number"</code> to still render the text field with a
+  useful width.</p>
+
   <p class=note>In <a href=#syntax>the HTML syntax</a>, specifying a <a href=#syntax-doctype title=syntax-DOCTYPE>DOCTYPE</a> that is an <a href=#obsolete-permitted-doctype>obsolete
   permitted DOCTYPE</a> will also trigger a warning.</p>
 
@@ -91048,6 +91055,9 @@
    attribute on an <code><a href=#the-a-element>a</a></code> element, if its value is not the
    empty string.</li>
 
+   <li><p>The presence of a <code title=attr-input-maxlength><a href=#attr-input-maxlength>maxlength</a></code> attribute on
+   an <code><a href=#the-input-element>input</a></code> element whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#number-state title=attr-input-type-number>Number</a> state.</li>
+
   </ul><p>Conformance checkers must distinguish between pages that have no
   conformance errors and have none of these obsolete features, and
   pages that have no conformance errors but do have some of these

Modified: source
===================================================================
--- source	2011-08-10 22:56:55 UTC (rev 6412)
+++ source	2011-08-10 23:54:57 UTC (rev 6413)
@@ -108339,6 +108339,17 @@
   title="URL">URLs</span>. The <code title="attr-id">id</code>
   attribute should be used instead.</p>
 
+  <!-- remove this once type=number is widely supported -->
+  <p>Authors should not specify the <code
+  title="attr-input-maxlength">maxlength</code> attribute on
+  <code>input</code> elements whose <code
+  title="attr-input-type">type</code> attribute is in the <span
+  title="attr-input-type-number">Number</span> state. One valid reason
+  for using the attribute regardless is to help legacy user agents
+  that do not support <code>input</code> elements with <code
+  title="">type="number"</code> to still render the text field with a
+  useful width.</p>
+
   <p class="note">In <span>the HTML syntax</span>, specifying a <span
   title="syntax-DOCTYPE">DOCTYPE</span> that is an <span>obsolete
   permitted DOCTYPE</span> will also trigger a warning.</p>
@@ -108384,6 +108395,12 @@
    attribute on an <code>a</code> element, if its value is not the
    empty string.</p></li>
 
+   <li><p>The presence of a <code
+   title="attr-input-maxlength">maxlength</code> attribute on
+   an <code>input</code> element whose <code
+   title="attr-input-type">type</code> attribute is in the <span
+   title="attr-input-type-number">Number</span> state.</p></li>
+
   </ul>
 
   <p>Conformance checkers must distinguish between pages that have no