[Bug 21830] KeyboardEvent.locale is too general.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21830

Masayuki Nakano <masayuki@d-toybox.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |masayuki@d-toybox.com

--- Comment #1 from Masayuki Nakano <masayuki@d-toybox.com> ---
It's good timing. I tried implementing KeyboardEvent.locale and
CompositionEvent.locale on Gecko.

Then, I worked on Windows and Mac. I think there is no API on Linux (except
directly accessing IM framework such as iBus, SCIM). I'm still investigating
about Android, though.

On Windows, we can make conversion table with:
http://msdn.microsoft.com/en-us/goglobal/bb896001.aspx
# I guess that IE 9 also used this table.

On Mac, we can get the language property of current TIS with
kTISPropertyInputSourceLanguages.
https://developer.apple.com/library/mac/#documentation/TextFonts/Reference/TextInputSourcesReference/Reference/reference.html

Then, on Mac, we cannot return locale. E.g., cannot return en-US, can just
return en.

And IE 10 returns "zh-CN" for simplified Chinese. However, on Mac, we can
returns "zh-Hans". So, I have no idea to implement with good compatibility
between platforms.

So, I'm now thinking that .locale is not useful for web developers under
current spec.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 30 April 2013 00:00:05 UTC