- From: <bugzilla@jessica.w3.org>
- Date: 2014年6月04日 00:43:55 +0000
- To: www-dom@w3.org
- Message-ID: <bug-25968-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25968 Bug ID: 25968 Summary: Needs clearer definition of virtual keyboard's KeyboardEvent.code value if it doesn't emulate physical key event completely 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 [09:33] <masayuki> If a VKB doesn't emulate native physical key event completely, there are 2 patterns: [09:34] <masayuki> One is there is an API to compute scancode from virtual keycode. This is Windows' case. At this time, browsers can use the API and compute .code value from the result. [09:35] <Travis> I filed a bug for us to start investigating tests: https://www.w3.org/Bugs/Public/show_bug.cgi?id=25967 [09:36] <masayuki> The other is, the is not such API. E.g., Android. At this time, browsers can guess non-printable keys and some printable keys which can guess the key position from virtual keycode name. E.g., it has NUMPAD or something. [09:36] <garykac> I don't expect all VKBs to provide useful 'code' values for every key. [09:36] <garykac> They should if they want to emulate a physical keyboard, but not all VKBs care about that. [09:37] <masayuki> In the latter case, browsers should NOT set .code values for printable keys which must be in standard position because VK -> SC depends on keyboard layout. [09:39] <masayuki> https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#code-virtual-keyboards [09:39] <garykac> VKBs that emulate a physical keyboard should be emulating a particular layout as well - so they should know what positions to use. [09:39] <masayuki> This looks like that D3E spec recommends that browsers should guess the key position even in such case. [09:40] <garykac> So I would expect a virtual french keyboard (with standard layout) to use 'KeyA' for the key labeled 'q'. [09:41] <garykac> If they completely change the layout for the VKB, then the 'code' doesn't have much use. [09:41] <masayuki> I'd like you to document about the latter case in the spec even if the VKB looks like emulating physical keyboard but not generating scancode properly. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Wednesday, 4 June 2014 00:43:57 UTC