[Bug 11449] The current specification and implementation of <input type="date"> using yyyy-mm-dd format will be unacceptable to many of our corporate customers. Also, only allowing times in <input type="date"> to be in 24 hour clock will cause serious delays in our b


--- Comment #8 from Tab Atkins Jr. <jackalmage@gmail.com> 2010-12-01 21:36:06 UTC ---
(In reply to comment #7)
> Shelley is right -- I think the contributor was confused about display vs.
> internal formats, but he's still asking for the ability to choose specific
> output formats other than the browser locale.  This is probably a good feature
> to have, but as Philip says in comment 1, it's probably a CSS thing.

I don't believe that can be reliably inferred from the OP.  The OP had the
standard confusion between displayed value and submitted value.  The request
for more control over the displayed value is sufficiently vague that it can
easily be interpreted to be satisfied by the existing spec text.

However, if we assume that the OP *was* asking for direct author control over
the display of dates and times, then, well, that's a horrible idea.  The entire
*point* of the datetime inputs is to offer the display in whatever fashion the
user most desires.  Giving control over this to the author defeats that and is
directly and explicitly bad for i18n.  If I were European and was used to
seeing dates as "DD/MM/YYYY", I would *not* want an ignorant American developer
setting the displayed value to use the format "MM-DD-YYYY", *especially* if I'm
used to other sites leaving the displayed value to the default so the browser
respects my locale conventions.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 1 December 2010 21:36:08 UTC