"Eisu" (英数) key of JIS keyboard for Mac shouldn't be mapped with "RomanCharacters"

RESOLVED FIXED in mozilla37

Status

()

Core
DOM: Events
RESOLVED FIXED
4 years ago
a year ago

People

(Reporter: masayuki, Assigned: masayuki)

Tracking

({dev-doc-complete, inputmethod})

Trunk
mozilla37
x86_64
All
dev-doc-complete, inputmethod
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [u= c= p=0])

Attachments

(1 attachment)

I think that my mapping in bug 842927 is wrong for the "Eisu" (英数) key of JIS keyboard for Mac.

The key doesn't make "Roman character input mode" enable. The key closes IME on Mac (I'm not sure how it works with Android 4.1 and later). So, the key should be "Alphanumeric" or something new key name.

I posted this to the bugzilla of w3.org.
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22750

Anyway, we need to remap the key name in the future.
Whiteboard: [u= c= p=0]
Blocks: 900372
Status: NEW → ASSIGNED
Depends on: 936315
Created attachment 8445202 [details] [diff] [review]
Support "Eisu" key value on Mac, Android and Gonk

Japanese keyboard layout has two different Eisu (英数) keys. One is the left of KeyA of PC keyboard. The other is the left of space key of Mac keyboard. I.e., they are never existing on same physical keyboard (usually).

They work really different. The former is typically used for changing IME input mode to ASCII capable. The latter is typically used for closing IME. Therefore, D3E-key defines "Alphanumeric" for the former and "Eisu" for the latter.

These names are messy. But since they have really different purpose, D3E-key value should distinguish them.

https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3Events-key.html#key-Eisu
https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3Events-key.html#key-Alphanumeric
Attachment #8445202 - Flags: review?(smichaud)
Attachment #8445202 - Flags: review?(nchen)
Attachment #8445202 - Flags: review?(mwu)
Attachment #8445202 - Flags: review?(bugs)
FYI: We've already mapped them as "RomanCharacters" (which has already renamed to "Romaji"). The definition of the key by renaming the key name causes this mapping is really wrong. Therefore, "Eisu" is defined for the Mac keyboard's "Eisu" key.
Comment on attachment 8445202 [details] [diff] [review]
Support "Eisu" key value on Mac, Android and Gonk

This looks reasonable to me.  But there are some things I don't understand.

What are we going to do about the "Alphanumeric" key?  Why isn't the Android key name "Alphanumeric" instead of "Eisu"?  (I assume Android would use what you've called a "PC keyboard".)
Attachment #8445202 - Flags: review?(smichaud) → review+
(In reply to Steven Michaud from comment #3)
> What are we going to do about the "Alphanumeric" key?  Why isn't the Android
> key name "Alphanumeric" instead of "Eisu"?  (I assume Android would use what
> you've called a "PC keyboard".)

Good point.

The Eisu key on PC keyboard is also CapsLock key. On Windows, Eisu key causes changing IME input mode to ASCII capable mode in most IMEs. Additionally, Shift + Eisu is CapsLock.

On Linux, it depends on system settings. On some environments, the key works as like the key on Windows. On others, the key works just as CapsLock key.

On Android, it works just a CapsLock key. Therefore, in software level, there is no PC-Eisu key on Android. However, Android has a key code for Eisu key of Japanese Mac Keyboard. The key code is used only for the key.
Attachment #8445202 - Flags: review?(nchen) → review+

Updated

3 years ago
Attachment #8445202 - Flags: review?(mwu) → review+

Updated

3 years ago
Attachment #8445202 - Flags: review?(bugs) → review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/62246121651b
https://hg.mozilla.org/mozilla-central/rev/62246121651b
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla37
This has been corrected on the KeyboardEvent.key page on MDN during a total rewrite I'm doing there. KeyboardEvent.code has not been done yet.
Keywords: dev-doc-needed
This has also been noted now (at last) on Firefox 37 for developers. Still need to update KeyboardEvent.code. It's on my to-do list.
This has now been updated in KeyboardEvent.code. This is now doc complete.
Keywords: dev-doc-needed → dev-doc-complete
You need to log in before you can comment on or make changes to this bug.