- From: poot <cvsmail@w3.org>
- Date: Fri, 20 Jan 2012 18:03:41 -0500
- To: public-html-diffs@w3.org
hixie: Clarify how language affects form controls. (whatwg r6905)
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.5502&r2=1.5503&f=h
http://html5.org/tools/web-apps-tracker?from=6904&to=6905
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5502
retrieving revision 1.5503
diff -u -d -r1.5502 -r1.5503
--- Overview.html 20 Jan 2012 22:42:05 -0000 1.5502
+++ Overview.html 20 Jan 2012 23:03:26 -0000 1.5503
@@ -320,7 +320,7 @@
<h1>HTML5</h1>
<h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
- <h2 class="no-num no-toc" id="editor-s-draft-19-january-2012">Editor's Draft 19 January 2012</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-20-january-2012">Editor's Draft 20 January 2012</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -467,7 +467,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 19 January 2012 Editor's Draft.
+ This specification is the 20 January 2012 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -9420,8 +9420,11 @@
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). </p>
+ 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). </p>
+
+
<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>
@@ -35452,7 +35455,17 @@
</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>The <code title="attr-input-value"><a href="#attr-input-value">value</a></code> attribute, if
+ 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 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, but their browser,
+ configured to use the British English locale, only showed the date
+ 03/02 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>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><div class="impl">
Received on Friday, 20 January 2012 23:03:42 UTC