[html5] r6912 - [e] (0) Fix the changes in r6905 to be more consistent and thorough. Fixing http [...]
whatwg at whatwg.org
whatwg at whatwg.org
Tue Jan 24 15:00:27 PST 2012
Author: ianh
Date: 2012-01-24 15:00:26 -0800 (Tue, 24 Jan 2012)
New Revision: 6912
Modified:
complete.html
index
source
Log:
[e] (0) Fix the changes in r6905 to be more consistent and thorough.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=13408
Affected topics: HTML
Modified: complete.html
===================================================================
--- complete.html 2012-01-24 22:39:20 UTC (rev 6911)
+++ complete.html 2012-01-24 23:00:26 UTC (rev 6912)
@@ -651,7 +651,7 @@
<li><a href=#implementing-the-server-side-processing-for-a-form><span class=secno>4.10.1.2 </span>Implementing the server-side processing for a form</a></li>
<li><a href=#configuring-a-form-to-communicate-with-a-server><span class=secno>4.10.1.3 </span>Configuring a form to communicate with a server</a></li>
<li><a href=#client-side-form-validation><span class=secno>4.10.1.4 </span>Client-side form validation</a></li>
- <li><a href=#date-and-time-formats><span class=secno>4.10.1.5 </span>Date and time formats</a></ol></li>
+ <li><a href=#input-author-notes><span class=secno>4.10.1.5 </span>Date, time, and number formats</a></ol></li>
<li><a href=#categories><span class=secno>4.10.2 </span>Categories</a></li>
<li><a href=#the-form-element><span class=secno>4.10.3 </span>The <code>form</code> element</a></li>
<li><a href=#the-fieldset-element><span class=secno>4.10.4 </span>The <code>fieldset</code> element</a></li>
@@ -683,22 +683,23 @@
<li><a href="#image-button-state-(type=image)"><span class=secno>4.10.7.1.20 </span>Image Button state (<code title="">type=image</code>)</a></li>
<li><a href="#reset-button-state-(type=reset)"><span class=secno>4.10.7.1.21 </span>Reset Button state (<code title="">type=reset</code>)</a></li>
<li><a href="#button-state-(type=button)"><span class=secno>4.10.7.1.22 </span>Button state (<code title="">type=button</code>)</a></ol></li>
- <li><a href=#common-input-element-attributes><span class=secno>4.10.7.2 </span>Common <code>input</code> element attributes</a>
+ <li><a href=#input-impl-notes><span class=secno>4.10.7.2 </span>Implemention notes regarding localization of form controls</a></li>
+ <li><a href=#common-input-element-attributes><span class=secno>4.10.7.3 </span>Common <code>input</code> element attributes</a>
<ol>
- <li><a href=#the-autocomplete-attribute><span class=secno>4.10.7.2.1 </span>The <code title=attr-input-autocomplete>autocomplete</code> attribute</a></li>
- <li><a href=#the-dirname-attribute><span class=secno>4.10.7.2.2 </span>The <code title=attr-input-dirname>dirname</code> attribute</a></li>
- <li><a href=#the-list-attribute><span class=secno>4.10.7.2.3 </span>The <code title=attr-input-list>list</code> attribute</a></li>
- <li><a href=#the-readonly-attribute><span class=secno>4.10.7.2.4 </span>The <code title=attr-input-readonly>readonly</code> attribute</a></li>
- <li><a href=#the-size-attribute><span class=secno>4.10.7.2.5 </span>The <code title=attr-input-size>size</code> attribute</a></li>
- <li><a href=#the-required-attribute><span class=secno>4.10.7.2.6 </span>The <code title=attr-input-required>required</code> attribute</a></li>
- <li><a href=#the-multiple-attribute><span class=secno>4.10.7.2.7 </span>The <code title=attr-input-multiple>multiple</code> attribute</a></li>
- <li><a href=#the-maxlength-attribute><span class=secno>4.10.7.2.8 </span>The <code title=attr-input-maxlength>maxlength</code> attribute</a></li>
- <li><a href=#the-pattern-attribute><span class=secno>4.10.7.2.9 </span>The <code title=attr-input-pattern>pattern</code> attribute</a></li>
- <li><a href=#the-min-and-max-attributes><span class=secno>4.10.7.2.10 </span>The <code title=attr-input-min>min</code> and <code title=attr-input-max>max</code> attributes</a></li>
- <li><a href=#the-step-attribute><span class=secno>4.10.7.2.11 </span>The <code title=attr-input-step>step</code> attribute</a></li>
- <li><a href=#the-placeholder-attribute><span class=secno>4.10.7.2.12 </span>The <code title=attr-input-placeholder>placeholder</code> attribute</a></ol></li>
- <li><a href=#common-input-element-apis><span class=secno>4.10.7.3 </span>Common <code>input</code> element APIs</a></li>
- <li><a href=#common-event-behaviors><span class=secno>4.10.7.4 </span>Common event behaviors</a></ol></li>
+ <li><a href=#the-autocomplete-attribute><span class=secno>4.10.7.3.1 </span>The <code title=attr-input-autocomplete>autocomplete</code> attribute</a></li>
+ <li><a href=#the-dirname-attribute><span class=secno>4.10.7.3.2 </span>The <code title=attr-input-dirname>dirname</code> attribute</a></li>
+ <li><a href=#the-list-attribute><span class=secno>4.10.7.3.3 </span>The <code title=attr-input-list>list</code> attribute</a></li>
+ <li><a href=#the-readonly-attribute><span class=secno>4.10.7.3.4 </span>The <code title=attr-input-readonly>readonly</code> attribute</a></li>
+ <li><a href=#the-size-attribute><span class=secno>4.10.7.3.5 </span>The <code title=attr-input-size>size</code> attribute</a></li>
+ <li><a href=#the-required-attribute><span class=secno>4.10.7.3.6 </span>The <code title=attr-input-required>required</code> attribute</a></li>
+ <li><a href=#the-multiple-attribute><span class=secno>4.10.7.3.7 </span>The <code title=attr-input-multiple>multiple</code> attribute</a></li>
+ <li><a href=#the-maxlength-attribute><span class=secno>4.10.7.3.8 </span>The <code title=attr-input-maxlength>maxlength</code> attribute</a></li>
+ <li><a href=#the-pattern-attribute><span class=secno>4.10.7.3.9 </span>The <code title=attr-input-pattern>pattern</code> attribute</a></li>
+ <li><a href=#the-min-and-max-attributes><span class=secno>4.10.7.3.10 </span>The <code title=attr-input-min>min</code> and <code title=attr-input-max>max</code> attributes</a></li>
+ <li><a href=#the-step-attribute><span class=secno>4.10.7.3.11 </span>The <code title=attr-input-step>step</code> attribute</a></li>
+ <li><a href=#the-placeholder-attribute><span class=secno>4.10.7.3.12 </span>The <code title=attr-input-placeholder>placeholder</code> attribute</a></ol></li>
+ <li><a href=#common-input-element-apis><span class=secno>4.10.7.4 </span>Common <code>input</code> element APIs</a></li>
+ <li><a href=#common-event-behaviors><span class=secno>4.10.7.5 </span>Common event behaviors</a></ol></li>
<li><a href=#the-button-element><span class=secno>4.10.8 </span>The <code>button</code> element</a></li>
<li><a href=#the-select-element><span class=secno>4.10.9 </span>The <code>select</code> element</a></li>
<li><a href=#the-datalist-element><span class=secno>4.10.10 </span>The <code>datalist</code> element</a></li>
@@ -41565,7 +41566,7 @@
</form></pre>
- <h5 id=date-and-time-formats><span class=secno>4.10.1.5 </span>Date and time formats</h5>
+ <h5 id=input-author-notes><span class=secno>4.10.1.5 </span>Date, time, and number formats</h5>
<p><i>This section is non-normative.</i></p>
@@ -41581,17 +41582,20 @@
minutes using an "h" character, as in "14h00".</p>
<p>Similar issues exist with dates, with the added complication that
- even the order of the components is not always consistent; for
- example, in Cyprus the first of February 2003 would typically be
+ even the order of the components is not always consistent —
+ for example, in Cyprus the first of February 2003 would typically be
written "1/2/03", while that same date in Japan would typically be
- written as "2003年02月01日".</p>
+ written as "2003年02月01日" — and even with
+ numbers, where locales differ, for example, in what punctuation is
+ used as the decimal separator and the thousands separator.</p>
- <p>It therefore is important to distinguish the time and date format
- used in HTML and in form submissions, which are always the formats
- defined in this specification (and based on the well-established ISO
- 8601 standard for computer-readable date and time formats), from the
- time and date formats presented to the user by the browser and
- accepted as input from the user by the browser.</p>
+ <p>It therefore is important to distinguish the time, date, and
+ number formats used in HTML and in form submissions, which are
+ always the formats defined in this specification (and based on the
+ well-established ISO 8601 standard for computer-readable date and
+ time formats), from the time, date, and number formats presented to
+ the user by the browser and accepted as input from the user by the
+ browser.</p>
<p>The format used "on the wire", i.e. in HTML markup and in form
submissions, is intended to be computer-readable and consistent
@@ -41599,20 +41603,25 @@
written in the format "YYYY-MM-DD", as in "2003-02-01". Users are
not expected to ever see this format.</p>
- <p>The date or time given by the page in the wire format is then
- translated to the user's preferred presentation (based on user
+ <p>The time, date, or number given by the page in the wire format is
+ then translated to the user's preferred presentation (based on user
preferences or on the locale of the page itself), before being
- displayed to the user. Similarly, after the user inputs a date or
- time using their preferred format, the user agent converts it back
- to the wire format before putting it in the DOM or submitting it.</p>
+ displayed to the user. Similarly, after the user inputs a time,
+ date, or number using their preferred format, the user agent
+ converts it back to the wire format before putting it in the DOM or
+ submitting it.</p>
- <p>This allows scripts in pages and on servers to process dates and
- times in a consistent manner without needing to support dozens of
- different formats, while still supporting the users' needs.</p>
+ <p>This allows scripts in pages and on servers to process times,
+ dates, and numbers in a consistent manner without needing to support
+ dozens of different formats, while still supporting the users'
+ needs.</p>
+ <div class=impl>
+ <p class=note>See also the <a href=#input-impl-notes>implementation notes</a> regarding
+ localization of form controls.</p>
+ </div>
-
<h4 id=categories><span class=secno>4.10.2 </span>Categories</h4>
<p>Mostly for historical reasons, elements in this section fall into
@@ -44584,23 +44593,12 @@
</div>
- <p class=note>The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present dates and times according to the conventions
- of either the locale implied by the element's <a href=#language>language</a>
- or the user's preferred locale. Using the page locale will ensure
- consistency with page-provided data.</p>
+ <p class=note>See the <a href=#input-author-notes>introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class=impl>, and the <a href=#input-impl-notes>implementation notes</a> regarding
+ localization of form controls</span>.</p>
- <p class=Example>For example, it would be confusing to users if an
- American English page claimed that a Cirque De Soleil show was going
- to be showing on 02/03<!-- Feb 3 (year) -->, but their browser,
- configured to use the British English locale, only showed the date
- 03/02<!-- 3 Feb (year) --> in the ticket purchase date picker. Using
- the page's locale would at least ensure that the date was presented
- in the same format everywhere. (There's still a risk that the user
- would end up arriving a month late, of course, but there's only so
- much that can be done about such cultural differences...)</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-global-date-and-time-string>valid
global date and time string</a>.</p> <!-- ok to set out-of-range
@@ -44798,10 +44796,11 @@
</div>
- <p class=note>The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present dates according to the conventions of the
- user's preferred locale.</p>
+ <p class=note>See the <a href=#input-author-notes>introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class=impl>, and the <a href=#input-impl-notes>implementation notes</a> regarding
+ localization of form controls</span>.</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-date-string>valid
@@ -44951,13 +44950,14 @@
month string</a> representing the user's selection. User agents
should allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to the empty string.</p>
+ <p class=note>See the <a href=#input-author-notes>introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class=impl>, and the <a href=#input-impl-notes>implementation notes</a> regarding
+ localization of form controls</span>.</p>
+
</div>
- <p class=note>The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present months according to the conventions of the
- user's preferred locale.</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-month-string>valid
month string</a>.</p> <!-- ok to set out-of-range value, we never
@@ -45105,13 +45105,14 @@
week string</a> representing the user's selection. User agents
should allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to the empty string.</p>
+ <p class=note>See the <a href=#input-author-notes>introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class=impl>, and the <a href=#input-impl-notes>implementation notes</a> regarding
+ localization of form controls</span>.</p>
+
</div>
- <p class=note>The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present weeks according to the conventions of the
- user's preferred locale.</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-week-string>valid
week string</a>.</p> <!-- ok to set out-of-range value, we never
@@ -45263,13 +45264,14 @@
time string</a> representing the user's selection. User agents
should allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to the empty string.</p>
+ <p class=note>See the <a href=#input-author-notes>introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class=impl>, and the <a href=#input-impl-notes>implementation notes</a> regarding
+ localization of form controls</span>.</p>
+
</div>
- <p class=note>The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present times according to the conventions of the
- user's preferred locale.</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-time-string>valid
time string</a>.</p> <!-- ok to set out-of-range value, we never
@@ -45418,13 +45420,14 @@
string</a> representing the user's selection. User agents should
allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to the empty string.</p>
+ <p class=note>See the <a href=#input-author-notes>introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class=impl>, and the <a href=#input-impl-notes>implementation notes</a> regarding
+ localization of form controls</span>.</p>
+
</div>
- <p class=note>The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present dates and times according to the conventions
- of the user's preferred locale.</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-local-date-and-time-string>valid
local date and time string</a>.</p> <!-- ok to set out-of-range
@@ -46990,9 +46993,37 @@
</div>
+ <div class=impl>
- <h5 id=common-input-element-attributes><span class=secno>4.10.7.2 </span>Common <code><a href=#the-input-element>input</a></code> element attributes</h5>
+ <h5 id=input-impl-notes><span class=secno>4.10.7.2 </span>Implemention notes regarding localization of form controls</h5>
+ <p><i>This section is non-normative.</i></p>
+
+ <p>The formats shown to the user in date, time, and number controls
+ is independent of the format used for form submission.</p>
+
+ <p>Browsers are encouraged to use user interfaces that present
+ dates, times, and numbers according to the conventions of either the
+ locale implied by the <code><a href=#the-input-element>input</a></code> element's
+ <a href=#language>language</a> or the user's preferred locale. Using the
+ page's locale will ensure consistency with page-provided data.
+
+ <p class=example>For example, it would be confusing to users if an
+ American English page claimed that a Cirque De Soleil show was going
+ to be showing on 02/03<!-- Feb 3 (year) -->, but their browser,
+ configured to use the British English locale, only showed the date
+ 03/02<!-- 3 Feb (year) --> in the ticket purchase date picker. Using
+ the page's locale would at least ensure that the date was presented
+ in the same format everywhere. (There's still a risk that the user
+ would end up arriving a month late, of course, but there's only so
+ much that can be done about such cultural differences...)</p>
+
+ </div>
+
+
+
+ <h5 id=common-input-element-attributes><span class=secno>4.10.7.3 </span>Common <code><a href=#the-input-element>input</a></code> element attributes</h5>
+
<div class=impl>
<p>These attributes only apply to an <code><a href=#the-input-element>input</a></code> element if
@@ -47006,7 +47037,7 @@
</div>
- <h6 id=the-autocomplete-attribute><span class=secno>4.10.7.2.1 </span>The <code title=attr-input-autocomplete><a href=#attr-input-autocomplete>autocomplete</a></code> attribute</h6>
+ <h6 id=the-autocomplete-attribute><span class=secno>4.10.7.3.1 </span>The <code title=attr-input-autocomplete><a href=#attr-input-autocomplete>autocomplete</a></code> attribute</h6>
<p>User agents sometimes have features for helping users fill forms
in, for example prefilling the user's address based on earlier user
@@ -47110,7 +47141,7 @@
</div>
- <h6 id=the-dirname-attribute><span class=secno>4.10.7.2.2 </span>The <code title=attr-input-dirname><a href=#attr-input-dirname>dirname</a></code> attribute</h6>
+ <h6 id=the-dirname-attribute><span class=secno>4.10.7.3.2 </span>The <code title=attr-input-dirname><a href=#attr-input-dirname>dirname</a></code> attribute</h6>
<p>The <dfn id=attr-input-dirname title=attr-input-dirname><code>dirname</code></dfn>
attribute, when it applies, is a <a href=#form-control-dirname-attribute>form control <code title="">dirname</code> attribute</a>.</p>
@@ -47141,7 +47172,7 @@
</div>
- <h6 id=the-list-attribute><span class=secno>4.10.7.2.3 </span>The <code title=attr-input-list><a href=#attr-input-list>list</a></code> attribute</h6>
+ <h6 id=the-list-attribute><span class=secno>4.10.7.3.3 </span>The <code title=attr-input-list><a href=#attr-input-list>list</a></code> attribute</h6>
<p>The <dfn id=attr-input-list title=attr-input-list><code>list</code></dfn>
attribute is used to identify an element that lists predefined
@@ -47289,7 +47320,7 @@
- <h6 id=the-readonly-attribute><span class=secno>4.10.7.2.4 </span>The <code title=attr-input-readonly><a href=#attr-input-readonly>readonly</a></code> attribute</h6>
+ <h6 id=the-readonly-attribute><span class=secno>4.10.7.3.4 </span>The <code title=attr-input-readonly><a href=#attr-input-readonly>readonly</a></code> attribute</h6>
<p>The <dfn id=attr-input-readonly title=attr-input-readonly><code>readonly</code></dfn>
attribute is a <a href=#boolean-attribute>boolean attribute</a> that controls whether
@@ -47338,7 +47369,7 @@
- <h6 id=the-size-attribute><span class=secno>4.10.7.2.5 </span>The <code title=attr-input-size><a href=#attr-input-size>size</a></code> attribute</h6>
+ <h6 id=the-size-attribute><span class=secno>4.10.7.3.5 </span>The <code title=attr-input-size><a href=#attr-input-size>size</a></code> attribute</h6>
<p>The <dfn id=attr-input-size title=attr-input-size><code>size</code></dfn>
attribute gives the number of characters that, in a visual
@@ -47364,7 +47395,7 @@
- <h6 id=the-required-attribute><span class=secno>4.10.7.2.6 </span>The <code title=attr-input-required><a href=#attr-input-required>required</a></code> attribute</h6>
+ <h6 id=the-required-attribute><span class=secno>4.10.7.3.6 </span>The <code title=attr-input-required><a href=#attr-input-required>required</a></code> attribute</h6>
<p>The <dfn id=attr-input-required title=attr-input-required><code>required</code></dfn>
attribute is a <a href=#boolean-attribute>boolean attribute</a>. When specified, the
@@ -47407,7 +47438,7 @@
</div>
- <h6 id=the-multiple-attribute><span class=secno>4.10.7.2.7 </span>The <code title=attr-input-multiple><a href=#attr-input-multiple>multiple</a></code> attribute</h6>
+ <h6 id=the-multiple-attribute><span class=secno>4.10.7.3.7 </span>The <code title=attr-input-multiple><a href=#attr-input-multiple>multiple</a></code> attribute</h6>
<p>The <dfn id=attr-input-multiple title=attr-input-multiple><code>multiple</code></dfn>
attribute is a <a href=#boolean-attribute>boolean attribute</a> that indicates whether
@@ -47460,7 +47491,7 @@
</div>
- <h6 id=the-maxlength-attribute><span class=secno>4.10.7.2.8 </span>The <code title=attr-input-maxlength><a href=#attr-input-maxlength>maxlength</a></code> attribute</h6>
+ <h6 id=the-maxlength-attribute><span class=secno>4.10.7.3.8 </span>The <code title=attr-input-maxlength><a href=#attr-input-maxlength>maxlength</a></code> attribute</h6>
<p>The <dfn id=attr-input-maxlength title=attr-input-maxlength><code>maxlength</code></dfn>
attribute<span class=impl>, when it applies,</span> is a <a href=#attr-fe-maxlength title=attr-fe-maxlength>form control <code title="">maxlength</code> attribute</a><span class=impl>
@@ -47486,7 +47517,7 @@
- <h6 id=the-pattern-attribute><span class=secno>4.10.7.2.9 </span>The <code title=attr-input-pattern><a href=#attr-input-pattern>pattern</a></code> attribute</h6>
+ <h6 id=the-pattern-attribute><span class=secno>4.10.7.3.9 </span>The <code title=attr-input-pattern><a href=#attr-input-pattern>pattern</a></code> attribute</h6>
<p>The <dfn id=attr-input-pattern title=attr-input-pattern><code>pattern</code></dfn>
attribute specifies a regular expression against which the control's
@@ -47574,7 +47605,7 @@
- <h6 id=the-min-and-max-attributes><span class=secno>4.10.7.2.10 </span>The <code title=attr-input-min><a href=#attr-input-min>min</a></code> and <code title=attr-input-max><a href=#attr-input-max>max</a></code> attributes</h6>
+ <h6 id=the-min-and-max-attributes><span class=secno>4.10.7.3.10 </span>The <code title=attr-input-min><a href=#attr-input-min>min</a></code> and <code title=attr-input-max><a href=#attr-input-max>max</a></code> attributes</h6>
<p>The <dfn id=attr-input-min title=attr-input-min><code>min</code></dfn> and <dfn id=attr-input-max title=attr-input-max><code>max</code></dfn> attributes indicate
the allowed range of values for the element.</p>
@@ -47655,7 +47686,7 @@
</div>
- <h6 id=the-step-attribute><span class=secno>4.10.7.2.11 </span>The <code title=attr-input-step><a href=#attr-input-step>step</a></code> attribute</h6>
+ <h6 id=the-step-attribute><span class=secno>4.10.7.3.11 </span>The <code title=attr-input-step><a href=#attr-input-step>step</a></code> attribute</h6>
<p>The <dfn id=attr-input-step title=attr-input-step><code>step</code></dfn>
attribute indicates the granularity that is expected (and required)
@@ -47742,7 +47773,7 @@
- <h6 id=the-placeholder-attribute><span class=secno>4.10.7.2.12 </span>The <code title=attr-input-placeholder><a href=#attr-input-placeholder>placeholder</a></code> attribute</h6>
+ <h6 id=the-placeholder-attribute><span class=secno>4.10.7.3.12 </span>The <code title=attr-input-placeholder><a href=#attr-input-placeholder>placeholder</a></code> attribute</h6>
<!-- similar text in the <textarea> section -->
@@ -47789,7 +47820,7 @@
<!--TOPIC:DOM APIs-->
- <h5 id=common-input-element-apis><span class=secno>4.10.7.3 </span>Common <code><a href=#the-input-element>input</a></code> element APIs</h5>
+ <h5 id=common-input-element-apis><span class=secno>4.10.7.4 </span>Common <code><a href=#the-input-element>input</a></code> element APIs</h5>
<dl class=domintro><dt><var title="">input</var> . <code title=dom-input-value><a href=#dom-input-value>value</a></code> [ = <var title="">value</var> ]</dt>
@@ -48067,7 +48098,7 @@
<div class=impl>
- <h5 id=common-event-behaviors><span class=secno>4.10.7.4 </span>Common event behaviors</h5>
+ <h5 id=common-event-behaviors><span class=secno>4.10.7.5 </span>Common event behaviors</h5>
<p>When the <dfn id=event-input-input title=event-input-input><code>input</code></dfn>
event applies, any time the user causes the element's <a href=#concept-fe-value title=concept-fe-value>value</a> to change, the user agent must
Modified: index
===================================================================
--- index 2012-01-24 22:39:20 UTC (rev 6911)
+++ index 2012-01-24 23:00:26 UTC (rev 6912)
@@ -651,7 +651,7 @@
<li><a href=#implementing-the-server-side-processing-for-a-form><span class=secno>4.10.1.2 </span>Implementing the server-side processing for a form</a></li>
<li><a href=#configuring-a-form-to-communicate-with-a-server><span class=secno>4.10.1.3 </span>Configuring a form to communicate with a server</a></li>
<li><a href=#client-side-form-validation><span class=secno>4.10.1.4 </span>Client-side form validation</a></li>
- <li><a href=#date-and-time-formats><span class=secno>4.10.1.5 </span>Date and time formats</a></ol></li>
+ <li><a href=#input-author-notes><span class=secno>4.10.1.5 </span>Date, time, and number formats</a></ol></li>
<li><a href=#categories><span class=secno>4.10.2 </span>Categories</a></li>
<li><a href=#the-form-element><span class=secno>4.10.3 </span>The <code>form</code> element</a></li>
<li><a href=#the-fieldset-element><span class=secno>4.10.4 </span>The <code>fieldset</code> element</a></li>
@@ -683,22 +683,23 @@
<li><a href="#image-button-state-(type=image)"><span class=secno>4.10.7.1.20 </span>Image Button state (<code title="">type=image</code>)</a></li>
<li><a href="#reset-button-state-(type=reset)"><span class=secno>4.10.7.1.21 </span>Reset Button state (<code title="">type=reset</code>)</a></li>
<li><a href="#button-state-(type=button)"><span class=secno>4.10.7.1.22 </span>Button state (<code title="">type=button</code>)</a></ol></li>
- <li><a href=#common-input-element-attributes><span class=secno>4.10.7.2 </span>Common <code>input</code> element attributes</a>
+ <li><a href=#input-impl-notes><span class=secno>4.10.7.2 </span>Implemention notes regarding localization of form controls</a></li>
+ <li><a href=#common-input-element-attributes><span class=secno>4.10.7.3 </span>Common <code>input</code> element attributes</a>
<ol>
- <li><a href=#the-autocomplete-attribute><span class=secno>4.10.7.2.1 </span>The <code title=attr-input-autocomplete>autocomplete</code> attribute</a></li>
- <li><a href=#the-dirname-attribute><span class=secno>4.10.7.2.2 </span>The <code title=attr-input-dirname>dirname</code> attribute</a></li>
- <li><a href=#the-list-attribute><span class=secno>4.10.7.2.3 </span>The <code title=attr-input-list>list</code> attribute</a></li>
- <li><a href=#the-readonly-attribute><span class=secno>4.10.7.2.4 </span>The <code title=attr-input-readonly>readonly</code> attribute</a></li>
- <li><a href=#the-size-attribute><span class=secno>4.10.7.2.5 </span>The <code title=attr-input-size>size</code> attribute</a></li>
- <li><a href=#the-required-attribute><span class=secno>4.10.7.2.6 </span>The <code title=attr-input-required>required</code> attribute</a></li>
- <li><a href=#the-multiple-attribute><span class=secno>4.10.7.2.7 </span>The <code title=attr-input-multiple>multiple</code> attribute</a></li>
- <li><a href=#the-maxlength-attribute><span class=secno>4.10.7.2.8 </span>The <code title=attr-input-maxlength>maxlength</code> attribute</a></li>
- <li><a href=#the-pattern-attribute><span class=secno>4.10.7.2.9 </span>The <code title=attr-input-pattern>pattern</code> attribute</a></li>
- <li><a href=#the-min-and-max-attributes><span class=secno>4.10.7.2.10 </span>The <code title=attr-input-min>min</code> and <code title=attr-input-max>max</code> attributes</a></li>
- <li><a href=#the-step-attribute><span class=secno>4.10.7.2.11 </span>The <code title=attr-input-step>step</code> attribute</a></li>
- <li><a href=#the-placeholder-attribute><span class=secno>4.10.7.2.12 </span>The <code title=attr-input-placeholder>placeholder</code> attribute</a></ol></li>
- <li><a href=#common-input-element-apis><span class=secno>4.10.7.3 </span>Common <code>input</code> element APIs</a></li>
- <li><a href=#common-event-behaviors><span class=secno>4.10.7.4 </span>Common event behaviors</a></ol></li>
+ <li><a href=#the-autocomplete-attribute><span class=secno>4.10.7.3.1 </span>The <code title=attr-input-autocomplete>autocomplete</code> attribute</a></li>
+ <li><a href=#the-dirname-attribute><span class=secno>4.10.7.3.2 </span>The <code title=attr-input-dirname>dirname</code> attribute</a></li>
+ <li><a href=#the-list-attribute><span class=secno>4.10.7.3.3 </span>The <code title=attr-input-list>list</code> attribute</a></li>
+ <li><a href=#the-readonly-attribute><span class=secno>4.10.7.3.4 </span>The <code title=attr-input-readonly>readonly</code> attribute</a></li>
+ <li><a href=#the-size-attribute><span class=secno>4.10.7.3.5 </span>The <code title=attr-input-size>size</code> attribute</a></li>
+ <li><a href=#the-required-attribute><span class=secno>4.10.7.3.6 </span>The <code title=attr-input-required>required</code> attribute</a></li>
+ <li><a href=#the-multiple-attribute><span class=secno>4.10.7.3.7 </span>The <code title=attr-input-multiple>multiple</code> attribute</a></li>
+ <li><a href=#the-maxlength-attribute><span class=secno>4.10.7.3.8 </span>The <code title=attr-input-maxlength>maxlength</code> attribute</a></li>
+ <li><a href=#the-pattern-attribute><span class=secno>4.10.7.3.9 </span>The <code title=attr-input-pattern>pattern</code> attribute</a></li>
+ <li><a href=#the-min-and-max-attributes><span class=secno>4.10.7.3.10 </span>The <code title=attr-input-min>min</code> and <code title=attr-input-max>max</code> attributes</a></li>
+ <li><a href=#the-step-attribute><span class=secno>4.10.7.3.11 </span>The <code title=attr-input-step>step</code> attribute</a></li>
+ <li><a href=#the-placeholder-attribute><span class=secno>4.10.7.3.12 </span>The <code title=attr-input-placeholder>placeholder</code> attribute</a></ol></li>
+ <li><a href=#common-input-element-apis><span class=secno>4.10.7.4 </span>Common <code>input</code> element APIs</a></li>
+ <li><a href=#common-event-behaviors><span class=secno>4.10.7.5 </span>Common event behaviors</a></ol></li>
<li><a href=#the-button-element><span class=secno>4.10.8 </span>The <code>button</code> element</a></li>
<li><a href=#the-select-element><span class=secno>4.10.9 </span>The <code>select</code> element</a></li>
<li><a href=#the-datalist-element><span class=secno>4.10.10 </span>The <code>datalist</code> element</a></li>
@@ -41565,7 +41566,7 @@
</form></pre>
- <h5 id=date-and-time-formats><span class=secno>4.10.1.5 </span>Date and time formats</h5>
+ <h5 id=input-author-notes><span class=secno>4.10.1.5 </span>Date, time, and number formats</h5>
<p><i>This section is non-normative.</i></p>
@@ -41581,17 +41582,20 @@
minutes using an "h" character, as in "14h00".</p>
<p>Similar issues exist with dates, with the added complication that
- even the order of the components is not always consistent; for
- example, in Cyprus the first of February 2003 would typically be
+ even the order of the components is not always consistent —
+ for example, in Cyprus the first of February 2003 would typically be
written "1/2/03", while that same date in Japan would typically be
- written as "2003年02月01日".</p>
+ written as "2003年02月01日" — and even with
+ numbers, where locales differ, for example, in what punctuation is
+ used as the decimal separator and the thousands separator.</p>
- <p>It therefore is important to distinguish the time and date format
- used in HTML and in form submissions, which are always the formats
- defined in this specification (and based on the well-established ISO
- 8601 standard for computer-readable date and time formats), from the
- time and date formats presented to the user by the browser and
- accepted as input from the user by the browser.</p>
+ <p>It therefore is important to distinguish the time, date, and
+ number formats used in HTML and in form submissions, which are
+ always the formats defined in this specification (and based on the
+ well-established ISO 8601 standard for computer-readable date and
+ time formats), from the time, date, and number formats presented to
+ the user by the browser and accepted as input from the user by the
+ browser.</p>
<p>The format used "on the wire", i.e. in HTML markup and in form
submissions, is intended to be computer-readable and consistent
@@ -41599,20 +41603,25 @@
written in the format "YYYY-MM-DD", as in "2003-02-01". Users are
not expected to ever see this format.</p>
- <p>The date or time given by the page in the wire format is then
- translated to the user's preferred presentation (based on user
+ <p>The time, date, or number given by the page in the wire format is
+ then translated to the user's preferred presentation (based on user
preferences or on the locale of the page itself), before being
- displayed to the user. Similarly, after the user inputs a date or
- time using their preferred format, the user agent converts it back
- to the wire format before putting it in the DOM or submitting it.</p>
+ displayed to the user. Similarly, after the user inputs a time,
+ date, or number using their preferred format, the user agent
+ converts it back to the wire format before putting it in the DOM or
+ submitting it.</p>
- <p>This allows scripts in pages and on servers to process dates and
- times in a consistent manner without needing to support dozens of
- different formats, while still supporting the users' needs.</p>
+ <p>This allows scripts in pages and on servers to process times,
+ dates, and numbers in a consistent manner without needing to support
+ dozens of different formats, while still supporting the users'
+ needs.</p>
+ <div class=impl>
+ <p class=note>See also the <a href=#input-impl-notes>implementation notes</a> regarding
+ localization of form controls.</p>
+ </div>
-
<h4 id=categories><span class=secno>4.10.2 </span>Categories</h4>
<p>Mostly for historical reasons, elements in this section fall into
@@ -44584,23 +44593,12 @@
</div>
- <p class=note>The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present dates and times according to the conventions
- of either the locale implied by the element's <a href=#language>language</a>
- or the user's preferred locale. Using the page locale will ensure
- consistency with page-provided data.</p>
+ <p class=note>See the <a href=#input-author-notes>introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class=impl>, and the <a href=#input-impl-notes>implementation notes</a> regarding
+ localization of form controls</span>.</p>
- <p class=Example>For example, it would be confusing to users if an
- American English page claimed that a Cirque De Soleil show was going
- to be showing on 02/03<!-- Feb 3 (year) -->, but their browser,
- configured to use the British English locale, only showed the date
- 03/02<!-- 3 Feb (year) --> in the ticket purchase date picker. Using
- the page's locale would at least ensure that the date was presented
- in the same format everywhere. (There's still a risk that the user
- would end up arriving a month late, of course, but there's only so
- much that can be done about such cultural differences...)</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-global-date-and-time-string>valid
global date and time string</a>.</p> <!-- ok to set out-of-range
@@ -44798,10 +44796,11 @@
</div>
- <p class=note>The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present dates according to the conventions of the
- user's preferred locale.</p>
+ <p class=note>See the <a href=#input-author-notes>introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class=impl>, and the <a href=#input-impl-notes>implementation notes</a> regarding
+ localization of form controls</span>.</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-date-string>valid
@@ -44951,13 +44950,14 @@
month string</a> representing the user's selection. User agents
should allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to the empty string.</p>
+ <p class=note>See the <a href=#input-author-notes>introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class=impl>, and the <a href=#input-impl-notes>implementation notes</a> regarding
+ localization of form controls</span>.</p>
+
</div>
- <p class=note>The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present months according to the conventions of the
- user's preferred locale.</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-month-string>valid
month string</a>.</p> <!-- ok to set out-of-range value, we never
@@ -45105,13 +45105,14 @@
week string</a> representing the user's selection. User agents
should allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to the empty string.</p>
+ <p class=note>See the <a href=#input-author-notes>introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class=impl>, and the <a href=#input-impl-notes>implementation notes</a> regarding
+ localization of form controls</span>.</p>
+
</div>
- <p class=note>The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present weeks according to the conventions of the
- user's preferred locale.</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-week-string>valid
week string</a>.</p> <!-- ok to set out-of-range value, we never
@@ -45263,13 +45264,14 @@
time string</a> representing the user's selection. User agents
should allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to the empty string.</p>
+ <p class=note>See the <a href=#input-author-notes>introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class=impl>, and the <a href=#input-impl-notes>implementation notes</a> regarding
+ localization of form controls</span>.</p>
+
</div>
- <p class=note>The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present times according to the conventions of the
- user's preferred locale.</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-time-string>valid
time string</a>.</p> <!-- ok to set out-of-range value, we never
@@ -45418,13 +45420,14 @@
string</a> representing the user's selection. User agents should
allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to the empty string.</p>
+ <p class=note>See the <a href=#input-author-notes>introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class=impl>, and the <a href=#input-impl-notes>implementation notes</a> regarding
+ localization of form controls</span>.</p>
+
</div>
- <p class=note>The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present dates and times according to the conventions
- of the user's preferred locale.</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-local-date-and-time-string>valid
local date and time string</a>.</p> <!-- ok to set out-of-range
@@ -46990,9 +46993,37 @@
</div>
+ <div class=impl>
- <h5 id=common-input-element-attributes><span class=secno>4.10.7.2 </span>Common <code><a href=#the-input-element>input</a></code> element attributes</h5>
+ <h5 id=input-impl-notes><span class=secno>4.10.7.2 </span>Implemention notes regarding localization of form controls</h5>
+ <p><i>This section is non-normative.</i></p>
+
+ <p>The formats shown to the user in date, time, and number controls
+ is independent of the format used for form submission.</p>
+
+ <p>Browsers are encouraged to use user interfaces that present
+ dates, times, and numbers according to the conventions of either the
+ locale implied by the <code><a href=#the-input-element>input</a></code> element's
+ <a href=#language>language</a> or the user's preferred locale. Using the
+ page's locale will ensure consistency with page-provided data.
+
+ <p class=example>For example, it would be confusing to users if an
+ American English page claimed that a Cirque De Soleil show was going
+ to be showing on 02/03<!-- Feb 3 (year) -->, but their browser,
+ configured to use the British English locale, only showed the date
+ 03/02<!-- 3 Feb (year) --> in the ticket purchase date picker. Using
+ the page's locale would at least ensure that the date was presented
+ in the same format everywhere. (There's still a risk that the user
+ would end up arriving a month late, of course, but there's only so
+ much that can be done about such cultural differences...)</p>
+
+ </div>
+
+
+
+ <h5 id=common-input-element-attributes><span class=secno>4.10.7.3 </span>Common <code><a href=#the-input-element>input</a></code> element attributes</h5>
+
<div class=impl>
<p>These attributes only apply to an <code><a href=#the-input-element>input</a></code> element if
@@ -47006,7 +47037,7 @@
</div>
- <h6 id=the-autocomplete-attribute><span class=secno>4.10.7.2.1 </span>The <code title=attr-input-autocomplete><a href=#attr-input-autocomplete>autocomplete</a></code> attribute</h6>
+ <h6 id=the-autocomplete-attribute><span class=secno>4.10.7.3.1 </span>The <code title=attr-input-autocomplete><a href=#attr-input-autocomplete>autocomplete</a></code> attribute</h6>
<p>User agents sometimes have features for helping users fill forms
in, for example prefilling the user's address based on earlier user
@@ -47110,7 +47141,7 @@
</div>
- <h6 id=the-dirname-attribute><span class=secno>4.10.7.2.2 </span>The <code title=attr-input-dirname><a href=#attr-input-dirname>dirname</a></code> attribute</h6>
+ <h6 id=the-dirname-attribute><span class=secno>4.10.7.3.2 </span>The <code title=attr-input-dirname><a href=#attr-input-dirname>dirname</a></code> attribute</h6>
<p>The <dfn id=attr-input-dirname title=attr-input-dirname><code>dirname</code></dfn>
attribute, when it applies, is a <a href=#form-control-dirname-attribute>form control <code title="">dirname</code> attribute</a>.</p>
@@ -47141,7 +47172,7 @@
</div>
- <h6 id=the-list-attribute><span class=secno>4.10.7.2.3 </span>The <code title=attr-input-list><a href=#attr-input-list>list</a></code> attribute</h6>
+ <h6 id=the-list-attribute><span class=secno>4.10.7.3.3 </span>The <code title=attr-input-list><a href=#attr-input-list>list</a></code> attribute</h6>
<p>The <dfn id=attr-input-list title=attr-input-list><code>list</code></dfn>
attribute is used to identify an element that lists predefined
@@ -47289,7 +47320,7 @@
- <h6 id=the-readonly-attribute><span class=secno>4.10.7.2.4 </span>The <code title=attr-input-readonly><a href=#attr-input-readonly>readonly</a></code> attribute</h6>
+ <h6 id=the-readonly-attribute><span class=secno>4.10.7.3.4 </span>The <code title=attr-input-readonly><a href=#attr-input-readonly>readonly</a></code> attribute</h6>
<p>The <dfn id=attr-input-readonly title=attr-input-readonly><code>readonly</code></dfn>
attribute is a <a href=#boolean-attribute>boolean attribute</a> that controls whether
@@ -47338,7 +47369,7 @@
- <h6 id=the-size-attribute><span class=secno>4.10.7.2.5 </span>The <code title=attr-input-size><a href=#attr-input-size>size</a></code> attribute</h6>
+ <h6 id=the-size-attribute><span class=secno>4.10.7.3.5 </span>The <code title=attr-input-size><a href=#attr-input-size>size</a></code> attribute</h6>
<p>The <dfn id=attr-input-size title=attr-input-size><code>size</code></dfn>
attribute gives the number of characters that, in a visual
@@ -47364,7 +47395,7 @@
- <h6 id=the-required-attribute><span class=secno>4.10.7.2.6 </span>The <code title=attr-input-required><a href=#attr-input-required>required</a></code> attribute</h6>
+ <h6 id=the-required-attribute><span class=secno>4.10.7.3.6 </span>The <code title=attr-input-required><a href=#attr-input-required>required</a></code> attribute</h6>
<p>The <dfn id=attr-input-required title=attr-input-required><code>required</code></dfn>
attribute is a <a href=#boolean-attribute>boolean attribute</a>. When specified, the
@@ -47407,7 +47438,7 @@
</div>
- <h6 id=the-multiple-attribute><span class=secno>4.10.7.2.7 </span>The <code title=attr-input-multiple><a href=#attr-input-multiple>multiple</a></code> attribute</h6>
+ <h6 id=the-multiple-attribute><span class=secno>4.10.7.3.7 </span>The <code title=attr-input-multiple><a href=#attr-input-multiple>multiple</a></code> attribute</h6>
<p>The <dfn id=attr-input-multiple title=attr-input-multiple><code>multiple</code></dfn>
attribute is a <a href=#boolean-attribute>boolean attribute</a> that indicates whether
@@ -47460,7 +47491,7 @@
</div>
- <h6 id=the-maxlength-attribute><span class=secno>4.10.7.2.8 </span>The <code title=attr-input-maxlength><a href=#attr-input-maxlength>maxlength</a></code> attribute</h6>
+ <h6 id=the-maxlength-attribute><span class=secno>4.10.7.3.8 </span>The <code title=attr-input-maxlength><a href=#attr-input-maxlength>maxlength</a></code> attribute</h6>
<p>The <dfn id=attr-input-maxlength title=attr-input-maxlength><code>maxlength</code></dfn>
attribute<span class=impl>, when it applies,</span> is a <a href=#attr-fe-maxlength title=attr-fe-maxlength>form control <code title="">maxlength</code> attribute</a><span class=impl>
@@ -47486,7 +47517,7 @@
- <h6 id=the-pattern-attribute><span class=secno>4.10.7.2.9 </span>The <code title=attr-input-pattern><a href=#attr-input-pattern>pattern</a></code> attribute</h6>
+ <h6 id=the-pattern-attribute><span class=secno>4.10.7.3.9 </span>The <code title=attr-input-pattern><a href=#attr-input-pattern>pattern</a></code> attribute</h6>
<p>The <dfn id=attr-input-pattern title=attr-input-pattern><code>pattern</code></dfn>
attribute specifies a regular expression against which the control's
@@ -47574,7 +47605,7 @@
- <h6 id=the-min-and-max-attributes><span class=secno>4.10.7.2.10 </span>The <code title=attr-input-min><a href=#attr-input-min>min</a></code> and <code title=attr-input-max><a href=#attr-input-max>max</a></code> attributes</h6>
+ <h6 id=the-min-and-max-attributes><span class=secno>4.10.7.3.10 </span>The <code title=attr-input-min><a href=#attr-input-min>min</a></code> and <code title=attr-input-max><a href=#attr-input-max>max</a></code> attributes</h6>
<p>The <dfn id=attr-input-min title=attr-input-min><code>min</code></dfn> and <dfn id=attr-input-max title=attr-input-max><code>max</code></dfn> attributes indicate
the allowed range of values for the element.</p>
@@ -47655,7 +47686,7 @@
</div>
- <h6 id=the-step-attribute><span class=secno>4.10.7.2.11 </span>The <code title=attr-input-step><a href=#attr-input-step>step</a></code> attribute</h6>
+ <h6 id=the-step-attribute><span class=secno>4.10.7.3.11 </span>The <code title=attr-input-step><a href=#attr-input-step>step</a></code> attribute</h6>
<p>The <dfn id=attr-input-step title=attr-input-step><code>step</code></dfn>
attribute indicates the granularity that is expected (and required)
@@ -47742,7 +47773,7 @@
- <h6 id=the-placeholder-attribute><span class=secno>4.10.7.2.12 </span>The <code title=attr-input-placeholder><a href=#attr-input-placeholder>placeholder</a></code> attribute</h6>
+ <h6 id=the-placeholder-attribute><span class=secno>4.10.7.3.12 </span>The <code title=attr-input-placeholder><a href=#attr-input-placeholder>placeholder</a></code> attribute</h6>
<!-- similar text in the <textarea> section -->
@@ -47789,7 +47820,7 @@
<!--TOPIC:DOM APIs-->
- <h5 id=common-input-element-apis><span class=secno>4.10.7.3 </span>Common <code><a href=#the-input-element>input</a></code> element APIs</h5>
+ <h5 id=common-input-element-apis><span class=secno>4.10.7.4 </span>Common <code><a href=#the-input-element>input</a></code> element APIs</h5>
<dl class=domintro><dt><var title="">input</var> . <code title=dom-input-value><a href=#dom-input-value>value</a></code> [ = <var title="">value</var> ]</dt>
@@ -48067,7 +48098,7 @@
<div class=impl>
- <h5 id=common-event-behaviors><span class=secno>4.10.7.4 </span>Common event behaviors</h5>
+ <h5 id=common-event-behaviors><span class=secno>4.10.7.5 </span>Common event behaviors</h5>
<p>When the <dfn id=event-input-input title=event-input-input><code>input</code></dfn>
event applies, any time the user causes the element's <a href=#concept-fe-value title=concept-fe-value>value</a> to change, the user agent must
Modified: source
===================================================================
--- source 2012-01-24 22:39:20 UTC (rev 6911)
+++ source 2012-01-24 23:00:26 UTC (rev 6912)
@@ -48517,7 +48517,7 @@
</form></pre>
- <h5>Date and time formats</h5>
+ <h5 id="input-author-notes">Date, time, and number formats</h5>
<!--END dev-html--><p><i>This section is non-normative.</i></p><!--START dev-html-->
@@ -48533,17 +48533,20 @@
minutes using an "h" character, as in "14h00".</p>
<p>Similar issues exist with dates, with the added complication that
- even the order of the components is not always consistent; for
- example, in Cyprus the first of February 2003 would typically be
+ even the order of the components is not always consistent —
+ for example, in Cyprus the first of February 2003 would typically be
written "1/2/03", while that same date in Japan would typically be
- written as "2003年02月01日".</p>
+ written as "2003年02月01日" — and even with
+ numbers, where locales differ, for example, in what punctuation is
+ used as the decimal separator and the thousands separator.</p>
- <p>It therefore is important to distinguish the time and date format
- used in HTML and in form submissions, which are always the formats
- defined in this specification (and based on the well-established ISO
- 8601 standard for computer-readable date and time formats), from the
- time and date formats presented to the user by the browser and
- accepted as input from the user by the browser.</p>
+ <p>It therefore is important to distinguish the time, date, and
+ number formats used in HTML and in form submissions, which are
+ always the formats defined in this specification (and based on the
+ well-established ISO 8601 standard for computer-readable date and
+ time formats), from the time, date, and number formats presented to
+ the user by the browser and accepted as input from the user by the
+ browser.</p>
<p>The format used "on the wire", i.e. in HTML markup and in form
submissions, is intended to be computer-readable and consistent
@@ -48551,20 +48554,26 @@
written in the format "YYYY-MM-DD", as in "2003-02-01". Users are
not expected to ever see this format.</p>
- <p>The date or time given by the page in the wire format is then
- translated to the user's preferred presentation (based on user
+ <p>The time, date, or number given by the page in the wire format is
+ then translated to the user's preferred presentation (based on user
preferences or on the locale of the page itself), before being
- displayed to the user. Similarly, after the user inputs a date or
- time using their preferred format, the user agent converts it back
- to the wire format before putting it in the DOM or submitting it.</p>
+ displayed to the user. Similarly, after the user inputs a time,
+ date, or number using their preferred format, the user agent
+ converts it back to the wire format before putting it in the DOM or
+ submitting it.</p>
- <p>This allows scripts in pages and on servers to process dates and
- times in a consistent manner without needing to support dozens of
- different formats, while still supporting the users' needs.</p>
+ <p>This allows scripts in pages and on servers to process times,
+ dates, and numbers in a consistent manner without needing to support
+ dozens of different formats, while still supporting the users'
+ needs.</p>
+ <div class="impl">
+ <p class="note">See also the <a
+ href="#input-impl-notes">implementation notes</a> regarding
+ localization of form controls.</p>
+ </div>
-
<h4>Categories</h4>
<p>Mostly for historical reasons, elements in this section fall into
@@ -51985,23 +51994,13 @@
</div>
- <p class="note">The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present dates and times according to the conventions
- of either the locale implied by the element's <span>language</span>
- or the user's preferred locale. Using the page locale will ensure
- consistency with page-provided data.</p>
+ <p class="note">See the <a href="#input-author-notes">introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class="impl">, and the <a
+ href="#input-impl-notes">implementation notes</a> regarding
+ localization of form controls</span>.</p>
- <p class="Example">For example, it would be confusing to users if an
- American English page claimed that a Cirque De Soleil show was going
- to be showing on 02/03<!-- Feb 3 (year) -->, but their browser,
- configured to use the British English locale, only showed the date
- 03/02<!-- 3 Feb (year) --> in the ticket purchase date picker. Using
- the page's locale would at least ensure that the date was presented
- in the same format everywhere. (There's still a risk that the user
- would end up arriving a month late, of course, but there's only so
- much that can be done about such cultural differences...)</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
global date and time string</span>.</p> <!-- ok to set out-of-range
@@ -52230,10 +52229,12 @@
</div>
- <p class="note">The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present dates according to the conventions of the
- user's preferred locale.</p>
+ <p class="note">See the <a href="#input-author-notes">introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class="impl">, and the <a
+ href="#input-impl-notes">implementation notes</a> regarding
+ localization of form controls</span>.</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
@@ -52407,13 +52408,15 @@
should allow the user to set the <span
title="concept-fe-value">value</span> to the empty string.</p>
+ <p class="note">See the <a href="#input-author-notes">introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class="impl">, and the <a
+ href="#input-impl-notes">implementation notes</a> regarding
+ localization of form controls</span>.</p>
+
</div>
- <p class="note">The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present months according to the conventions of the
- user's preferred locale.</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
month string</span>.</p> <!-- ok to set out-of-range value, we never
@@ -52583,13 +52586,15 @@
should allow the user to set the <span
title="concept-fe-value">value</span> to the empty string.</p>
+ <p class="note">See the <a href="#input-author-notes">introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class="impl">, and the <a
+ href="#input-impl-notes">implementation notes</a> regarding
+ localization of form controls</span>.</p>
+
</div>
- <p class="note">The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present weeks according to the conventions of the
- user's preferred locale.</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
week string</span>.</p> <!-- ok to set out-of-range value, we never
@@ -52765,13 +52770,15 @@
should allow the user to set the <span
title="concept-fe-value">value</span> to the empty string.</p>
+ <p class="note">See the <a href="#input-author-notes">introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class="impl">, and the <a
+ href="#input-impl-notes">implementation notes</a> regarding
+ localization of form controls</span>.</p>
+
</div>
- <p class="note">The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present times according to the conventions of the
- user's preferred locale.</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
time string</span>.</p> <!-- ok to set out-of-range value, we never
@@ -52938,13 +52945,15 @@
allow the user to set the <span
title="concept-fe-value">value</span> to the empty string.</p>
+ <p class="note">See the <a href="#input-author-notes">introduction
+ section</a> for a discussion of the difference between the input
+ format and submission format for date, time, and number form
+ controls<span class="impl">, and the <a
+ href="#input-impl-notes">implementation notes</a> regarding
+ localization of form controls</span>.</p>
+
</div>
- <p class="note">The format shown to the user is independent of the
- format used for form submission. Browsers are encouraged to use user
- interfaces that present dates and times according to the conventions
- of the user's preferred locale.</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
local date and time string</span>.</p> <!-- ok to set out-of-range
@@ -54715,7 +54724,35 @@
</div>
+ <div class="impl">
+ <h5 id="input-impl-notes">Implemention notes regarding localization of form controls</h5>
+
+ <!--END dev-html--><p><i>This section is non-normative.</i></p><!--START dev-html-->
+
+ <p>The formats shown to the user in date, time, and number controls
+ is independent of the format used for form submission.</p>
+
+ <p>Browsers are encouraged to use user interfaces that present
+ dates, times, and numbers according to the conventions of either the
+ locale implied by the <code>input</code> element's
+ <span>language</span> or the user's preferred locale. Using the
+ page's locale will ensure consistency with page-provided data.
+
+ <p class="example">For example, it would be confusing to users if an
+ American English page claimed that a Cirque De Soleil show was going
+ to be showing on 02/03<!-- Feb 3 (year) -->, but their browser,
+ configured to use the British English locale, only showed the date
+ 03/02<!-- 3 Feb (year) --> in the ticket purchase date picker. Using
+ the page's locale would at least ensure that the date was presented
+ in the same format everywhere. (There's still a risk that the user
+ would end up arriving a month late, of course, but there's only so
+ much that can be done about such cultural differences...)</p>
+
+ </div>
+
+
+
<h5>Common <code>input</code> element attributes</h5>
<div class="impl">
More information about the Commit-Watchers
mailing list