- From: <bugzilla@jessica.w3.org>
- Date: Wed, 27 Feb 2013 06:34:04 +0000
- To: www-dom@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21139 Bug ID: 21139 Summary: Define key name for Hankaku-Zenkaku key and Katakana-Hiragana key Classification: Unclassified Product: WebAppsWG Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P2 Component: DOM3 Events Assignee: travil@microsoft.com Reporter: masayuki@d-toybox.com QA Contact: public-webapps-bugzilla@w3.org CC: mike@w3.org, www-dom@w3.org Blocks: 21083 D3E defines key names, "FullWidth" (for Zenkaku), "HalfWidth" (for Hankaku), "Katakana" and "Hiragana". If the key actually sets the state to the named mode, it's okay. However, GTK, Qt and Android defines the keys as: GTK Qt Android GDK_Hiragana_Katakana Qt::Key_Hiragana_Katakana KEYCODE_KATAKANA_HIRAGANA GDK_Zenkaku_Hankaku Qt::Key_Zenkaku_Hankaku KEYCODE_ZENKAKU_HANKAKU Note that GTK and Qt also defines GDK_Hiragana Qt::Key_Hiragana GDK_Katakana Qt::Key_Katakana GDK_Zenkaku Qt::Key_Zenkaku GDK_Hankaku Qt::Key_Hankaku So, if the former key code values are mapped, we cannot use the key names for latter key code values. So, I think that 'ToggleFullWidthHalfWidth' or something and 'ToggleKatakanaHiragana' or something should be defined. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Wednesday, 27 February 2013 06:38:43 UTC