[html5] r7686 - [e] (0) Try adding yet more explanatory text. Fixing https://www.w3.org/Bugs/Pub [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2013-01-31 18:49:39 -0800 (Thu, 31 Jan 2013)
New Revision: 7686

Modified:
   complete.html
   index
   source
Log:
[e] (0) Try adding yet more explanatory text.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=17918
Affected topics: HTML

Modified: complete.html
===================================================================
--- complete.html	2013-02-01 00:18:54 UTC (rev 7685)
+++ complete.html	2013-02-01 02:49:39 UTC (rev 7686)
@@ -49007,9 +49007,13 @@
   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
+  submission as described above). Similarly, a user agent designed
   for Romans might display the value in Roman numerals rather than in
-  decimal.--></p>
+  decimal; or (more realistically) a user agent designed for the French
+  market might display the value with apostrophes between thousands and
+  commas before the decimals, and allow the user to enter a value in
+  that manner, internally converting it to the submission format
+  described above.</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
@@ -49122,6 +49126,12 @@
 
    <pre><label>How much do you want to charge? $<input type=number min=0 step=0.01 name=price></label></pre>
 
+   <p>As described above, a user agent might support numeric input in the user's local format,
+   converting it to the format required for submission as described above. This might include
+   handling grouping separators (as in "872,000,000,000") and various decimal separators (such as
+   "3,99" vs "3.99") or using local digits (such as those in Arabic, Devanagari, Persian, and
+   Thai).</p>
+
   </div>
 
   <p class=note>The <code title="">type=number</code> state is not

Modified: index
===================================================================
--- index	2013-02-01 00:18:54 UTC (rev 7685)
+++ index	2013-02-01 02:49:39 UTC (rev 7686)
@@ -49007,9 +49007,13 @@
   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
+  submission as described above). Similarly, a user agent designed
   for Romans might display the value in Roman numerals rather than in
-  decimal.--></p>
+  decimal; or (more realistically) a user agent designed for the French
+  market might display the value with apostrophes between thousands and
+  commas before the decimals, and allow the user to enter a value in
+  that manner, internally converting it to the submission format
+  described above.</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
@@ -49122,6 +49126,12 @@
 
    <pre><label>How much do you want to charge? $<input type=number min=0 step=0.01 name=price></label></pre>
 
+   <p>As described above, a user agent might support numeric input in the user's local format,
+   converting it to the format required for submission as described above. This might include
+   handling grouping separators (as in "872,000,000,000") and various decimal separators (such as
+   "3,99" vs "3.99") or using local digits (such as those in Arabic, Devanagari, Persian, and
+   Thai).</p>
+
   </div>
 
   <p class=note>The <code title="">type=number</code> state is not

Modified: source
===================================================================
--- source	2013-02-01 00:18:54 UTC (rev 7685)
+++ source	2013-02-01 02:49:39 UTC (rev 7686)
@@ -57208,9 +57208,13 @@
   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
+  submission as described above). Similarly, a user agent designed
   for Romans might display the value in Roman numerals rather than in
-  decimal.--></p>
+  decimal; or (more realistically) a user agent designed for the French
+  market might display the value with apostrophes between thousands and
+  commas before the decimals, and allow the user to enter a value in
+  that manner, internally converting it to the submission format
+  described above.</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
@@ -57327,6 +57331,12 @@
 
    <pre><label>How much do you want to charge? $<input type=number min=0 step=0.01 name=price></label></pre>
 
+   <p>As described above, a user agent might support numeric input in the user's local format,
+   converting it to the format required for submission as described above. This might include
+   handling grouping separators (as in "872,000,000,000") and various decimal separators (such as
+   "3,99" vs "3.99") or using local digits (such as those in Arabic, Devanagari, Persian, and
+   Thai).</p>
+
   </div>
 
   <p class="note">The <code title="">type=number</code> state is not