[html5] r6451 - [e] (0) Note on UI for type=number. Fixing http://www.w3.org/Bugs/Public/show_bu [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2011-08-14 20:51:24 -0700 (Sun, 14 Aug 2011)
New Revision: 6451

Modified:
   complete.html
   index
   source
Log:
[e] (0) Note on UI for type=number.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=12915

Modified: complete.html
===================================================================
--- complete.html	2011-08-15 03:45:26 UTC (rev 6450)
+++ complete.html	2011-08-15 03:51:24 UTC (rev 6451)
@@ -45864,6 +45864,15 @@
 
   </div>
 
+  <p class=note>This specification does not define what user
+  interface user agents are to use; user agent vendors are encouraged
+  to consider what would best serve their users' needs. For example, a
+  user agent in Persian or Arabic markets might support Persian and
+  Arabic numeric input (converting it to the format required for
+  submission as described above). <!--Similarly, a user agent designed
+  form Romans might display the value in Roman numerals rather than in
+  decimal.--></p>
+
   <p>The <code title=attr-input-value><a href=#attr-input-value>value</a></code> attribute, if
   specified and not empty, must have a value that is a <a href=#valid-floating-point-number>valid
   floating point number</a>.</p> <!-- ok to set out-of-range value,

Modified: index
===================================================================
--- index	2011-08-15 03:45:26 UTC (rev 6450)
+++ index	2011-08-15 03:51:24 UTC (rev 6451)
@@ -45731,6 +45731,15 @@
 
   </div>
 
+  <p class=note>This specification does not define what user
+  interface user agents are to use; user agent vendors are encouraged
+  to consider what would best serve their users' needs. For example, a
+  user agent in Persian or Arabic markets might support Persian and
+  Arabic numeric input (converting it to the format required for
+  submission as described above). <!--Similarly, a user agent designed
+  form Romans might display the value in Roman numerals rather than in
+  decimal.--></p>
+
   <p>The <code title=attr-input-value><a href=#attr-input-value>value</a></code> attribute, if
   specified and not empty, must have a value that is a <a href=#valid-floating-point-number>valid
   floating point number</a>.</p> <!-- ok to set out-of-range value,

Modified: source
===================================================================
--- source	2011-08-15 03:45:26 UTC (rev 6450)
+++ source	2011-08-15 03:51:24 UTC (rev 6451)
@@ -51202,6 +51202,15 @@
 
   </div>
 
+  <p class="note">This specification does not define what user
+  interface user agents are to use; user agent vendors are encouraged
+  to consider what would best serve their users' needs. For example, a
+  user agent in Persian or Arabic markets might support Persian and
+  Arabic numeric input (converting it to the format required for
+  submission as described above). <!--Similarly, a user agent designed
+  form Romans might display the value in Roman numerals rather than in
+  decimal.--></p>
+
   <p>The <code title="attr-input-value">value</code> attribute, if
   specified and not empty, must have a value that is a <span>valid
   floating point number</span>.</p> <!-- ok to set out-of-range value,