Comment #8 on issue 180 by franklin...@gmail.com: toLocaleDateString and
toLocaleTimeString do not honor the current locale
https://code.google.com/p/v8/issues/detail?id=180
I don't think still localeCompare api work as intended in chrome.
My Language and input setting of chrom is Swedish-sv
Comment #7 on issue 180 by js...@chromium.org: toLocaleDateString and
toLocaleTimeString do not honor the current locale
http://code.google.com/p/v8/issues/detail?id=180
toLocaleDateString, toLocaleTimeString, toLocaleCompare now behave
respecting the UI language of Chrome. That is, if you
Updates:
Status: WorkingAsIntended
Comment #6 on issue 180 by yang...@chromium.org: toLocaleDateString and
toLocaleTimeString do not honor the current locale
http://code.google.com/p/v8/issues/detail?id=180
refer to v8-i18n.
--
You received this message because this project is config
Comment #5 on issue 180 by travispuk: toLocaleDateString and
toLocaleTimeString do not honor the current locale
http://code.google.com/p/v8/issues/detail?id=180
When is this issue likely to be resolved?
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
Comment #4 on issue 180 by ianbmacdonald: toLocaleDateString and
toLocaleTimeString do not honor the current locale
http://code.google.com/p/v8/issues/detail?id=180
"Currently, the formats used in toLocaleDateString and toLocaleTimeString
are hard-coded, but they should be locale-dependent" .
Comment #3 on issue 180 by ApecHsing: toLocaleDateString and
toLocaleTimeString do not honor the current locale
http://code.google.com/p/v8/issues/detail?id=180
I focus on this issue for long time, but seems no any result,
it's same to 'localeCompare()' function.
--
v8-dev mailing list
v8-de
Comment #2 on issue 180 by egor.pavlikhin: toLocaleDateString and
toLocaleTimeString do not honor the current locale
http://code.google.com/p/v8/issues/detail?id=180
So what is happening with this issue?
How can I find out if user has 12-hour or 24-hour format on their machine?
--
v8-dev mai
