[html5] r6905 - [e] (0) Clarify how language affects form controls. Fixing http://www.w3.org/Bug [...]
whatwg at whatwg.org
whatwg at whatwg.org
Fri Jan 20 15:03:23 PST 2012
Author: ianh
Date: 2012-01-20 15:03:22 -0800 (Fri, 20 Jan 2012)
New Revision: 6905
Modified:
complete.html
index
source
Log:
[e] (0) Clarify how language affects form controls.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=13408
Affected topics: HTML
Modified: complete.html
===================================================================
--- complete.html 2012-01-20 22:41:57 UTC (rev 6904)
+++ complete.html 2012-01-20 23:03:22 UTC (rev 6905)
@@ -240,7 +240,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 19 January 2012</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 20 January 2012</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -11279,12 +11279,19 @@
unknown.</p>
<hr><p>User agents may use the element's language to determine proper
- processing or rendering (e.g. in the selection of appropriate
- fonts or pronunciations, or for dictionary selection). <!--User
- agents must not use the element's language to determine text
+ processing or rendering (e.g. in the selection of appropriate fonts
+ or pronunciations, for dictionary selection, or for the user
+ interfaces of form controls such as date pickers). <!--User agents
+ must not use the element's language to determine text
directionality. (commented out because text directionality is a
rendering-level concern.)--></p>
+ <!-- Date pickers would use the language information for determining
+ the language of months, for example. They should use the page's
+ _locale_ to figure out the format itself, not the language. There's
+ currently no way to determine the page's locale except by guessing
+ from the charset and language... -->
+
<hr><p>The <dfn id=dom-lang title=dom-lang><code>lang</code></dfn> IDL attribute
must <a href=#reflect>reflect</a> the <code title=attr-lang><a href=#attr-lang>lang</a></code>
content attribute in no namespace.</p>
@@ -44574,8 +44581,20 @@
<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>
+ 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=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
Modified: index
===================================================================
--- index 2012-01-20 22:41:57 UTC (rev 6904)
+++ index 2012-01-20 23:03:22 UTC (rev 6905)
@@ -240,7 +240,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 19 January 2012</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 20 January 2012</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -11279,12 +11279,19 @@
unknown.</p>
<hr><p>User agents may use the element's language to determine proper
- processing or rendering (e.g. in the selection of appropriate
- fonts or pronunciations, or for dictionary selection). <!--User
- agents must not use the element's language to determine text
+ processing or rendering (e.g. in the selection of appropriate fonts
+ or pronunciations, for dictionary selection, or for the user
+ interfaces of form controls such as date pickers). <!--User agents
+ must not use the element's language to determine text
directionality. (commented out because text directionality is a
rendering-level concern.)--></p>
+ <!-- Date pickers would use the language information for determining
+ the language of months, for example. They should use the page's
+ _locale_ to figure out the format itself, not the language. There's
+ currently no way to determine the page's locale except by guessing
+ from the charset and language... -->
+
<hr><p>The <dfn id=dom-lang title=dom-lang><code>lang</code></dfn> IDL attribute
must <a href=#reflect>reflect</a> the <code title=attr-lang><a href=#attr-lang>lang</a></code>
content attribute in no namespace.</p>
@@ -44574,8 +44581,20 @@
<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>
+ 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=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
Modified: source
===================================================================
--- source 2012-01-20 22:41:57 UTC (rev 6904)
+++ source 2012-01-20 23:03:22 UTC (rev 6905)
@@ -11687,12 +11687,19 @@
<hr>
<p>User agents may use the element's language to determine proper
- processing or rendering (e.g. in the selection of appropriate
- fonts or pronunciations, or for dictionary selection). <!--User
- agents must not use the element's language to determine text
+ processing or rendering (e.g. in the selection of appropriate fonts
+ or pronunciations, for dictionary selection, or for the user
+ interfaces of form controls such as date pickers). <!--User agents
+ must not use the element's language to determine text
directionality. (commented out because text directionality is a
rendering-level concern.)--></p>
+ <!-- Date pickers would use the language information for determining
+ the language of months, for example. They should use the page's
+ _locale_ to figure out the format itself, not the language. There's
+ currently no way to determine the page's locale except by guessing
+ from the charset and language... -->
+
<hr>
<p>The <dfn title="dom-lang"><code>lang</code></dfn> IDL attribute
@@ -51977,8 +51984,20 @@
<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>
+ 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="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
More information about the Commit-Watchers
mailing list