This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
4.10.7.1.7 Date and Time state http://dev.w3.org/html5/spec/single-page.html#date-and-time-state-type-datetime -- 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. -- Should we encourage the use of the *page's* preferred locale? It would be best if we could provide a way for page authors to create a consistent user experience. Work on the ECMAScript I18N extension may eventually help here, but only for formatting displayed values---this section seems to imply that the user agent have a built-in date/time control set that may not be scriptable. Although a given user agent won't necessarily support the requested locale, we would suggest providing a <form> attribute or a field attribute to allow the page itself to request a given locale using a BCP 47 language tag. The I18N WG feels that this could be accomplished by making section 4.10.7.2 normative.
This bug was cloned to create bug 17859 as part of operation convergence.
See also: https://www.w3.org/Bugs/Public/show_bug.cgi?id=16165 Number formats are also affected here. I think that this remains a significant gap in HTML, since having controls like dates or numbers be consistent with the page in which they appear is more pleasing to the author (and potentially less confusing to users) than having the controls be strictly in the locale of the user-agent's runtime.
HTML5.1 Bugzilla Bug Triage: Already Fixed See: http://w3c.github.io/html/sec-forms.html#implementation-notes > Browsers are encouraged to use user interfaces that present dates, times, and numbers according to the conventions of either the locale implied by the input element’s language or the user’s preferred locale. Using the page’s locale will ensure consistency with page-provided data. So, the language should be considered. Since there are already well-defined means of adding language information another new attribute isn't necessary. If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!