[html5] r6565 - [c] (0) Make size and maxlength conforming on type=number for now. (fixing r6413 [...]
whatwg at whatwg.org
whatwg at whatwg.org
Thu Sep 22 16:34:36 PDT 2011
Author: ianh
Date: 2011-09-22 16:34:34 -0700 (Thu, 22 Sep 2011)
New Revision: 6565
Modified:
complete.html
index
source
Log:
[c] (0) Make size and maxlength conforming on type=number for now. (fixing r6413 better)
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=12781
Modified: complete.html
===================================================================
--- complete.html 2011-09-22 23:21:04 UTC (rev 6564)
+++ complete.html 2011-09-22 23:34:34 UTC (rev 6565)
@@ -95177,11 +95177,14 @@
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>Authors should not, but may despite requirements to the contrary
+ elsewhere in this specification, specify the <code title=attr-input-maxlength><a href=#attr-input-maxlength>maxlength</a></code> and <code title=attr-input-size><a href=#attr-input-size>size</a></code> attributes 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> attributes
+ are in the <a href=#number-state title=attr-input-type-number>Number</a> state.
+ One valid reason for using these attributes 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>
@@ -95220,9 +95223,12 @@
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>
+ <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>
+ <li><p>The presence of a <code title=attr-input-size><a href=#attr-input-size>size</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-09-22 23:21:04 UTC (rev 6564)
+++ index 2011-09-22 23:34:34 UTC (rev 6565)
@@ -90602,11 +90602,14 @@
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>Authors should not, but may despite requirements to the contrary
+ elsewhere in this specification, specify the <code title=attr-input-maxlength><a href=#attr-input-maxlength>maxlength</a></code> and <code title=attr-input-size><a href=#attr-input-size>size</a></code> attributes 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> attributes
+ are in the <a href=#number-state title=attr-input-type-number>Number</a> state.
+ One valid reason for using these attributes 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>
@@ -90645,9 +90648,12 @@
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>
+ <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>
+ <li><p>The presence of a <code title=attr-input-size><a href=#attr-input-size>size</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-09-22 23:21:04 UTC (rev 6564)
+++ source 2011-09-22 23:34:34 UTC (rev 6565)
@@ -107875,15 +107875,16 @@
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>Authors should not, but may despite requirements to the contrary
+ elsewhere in this specification, specify the <code
+ title="attr-input-maxlength">maxlength</code> and <code
+ title="attr-input-size">size</code> attributes on <code>input</code>
+ elements whose <code title="attr-input-type">type</code> attributes
+ are in the <span title="attr-input-type-number">Number</span> state.
+ One valid reason for using these attributes 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
@@ -107931,11 +107932,17 @@
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-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>
+ <li><p>The presence of a <code
+ title="attr-input-size">size</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
More information about the Commit-Watchers
mailing list