Issue 3607: V8 returns incorrect localized values for JavaScript
toLocaleDateString and toLocaleTimeString
http://code.google.com/p/chromium/issues/detail?id=3607
Comment #5 by [EMAIL PROTECTED]:
I made a fix in V8 r645, but it only fixes the surface that brings Chrome
close to
Safari on Windows. As Ivan pointed out in review, we need someone who are
familiar
with Date and localization to make it work properly in all cases.
Here is what Ivan said:
LGTMForNow
I am OK with this change for "Mstone-1.0" only to make it look more like
Safari
on Windows: It appears that Safari 3.1.2 on Windows does not honor the local
machine setting for the Date formatting. Safari 3.1.2 on the Mac does
change the
output based on the system preference.
We should mark the fact that this is a quick hack in the bug and assign the
bug
to somebody knowledgeable about date formatting to fix the real "I18N"
issue.
Issue attribute updates:
Owner: ---
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
