Issue metadata
Sign in to add a comment
|
Japanese keyboard/JA input/英数: some keyboard shortcuts don't work |
||||||||||||||||||||||||
Issue descriptionWhat steps will reproduce the problem? 1. Install R58 9334.69.0 or R59 9460.60.0. Select JP during OOBE 2. Check KB layout is setting as JP (attachment: Setting.zip) 3. In OS, switch to 英数 (attached picture: switch key.jpg) 4. Open setting -> Device -> Keyboard -> View keyboard shortcuts (or press ctrl+alt+?) to call shortcuts layout reference 5. The layout look like JP KB 6. Base on this condition (step 3~5), there are some shortcuts no function or incorrect (attachment: shortcut_no function.pdf) What is the expected output? Shortcuts function workable as layout reference. What is the platform tested? reef What do you see instead? If switch to 英数, there are some keyboard shortcuts no function or not follow layout. How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Always could reproduce this problem. What is the impact to the user, and is there a workaround? If so, what is it? If user switch to 英数 and follow the shortcuts layout, there is wrong or no function. Please provide any additional information below. 1. The behavior is the same with image R58 9334.69.0 2. There is no other device with JP KB could be double check/compare on hand. 3. If switch to "かな", the shortcuts layout look like US (compare.png)
,
Jul 4 2017
,
Jul 5 2017
Can you please triage this.
,
Jul 5 2017
It seems to have the same root cause as crbug.com/300469.
,
Jul 5 2017
James, I think you recently took similar issue. Please take a look. Thank you.
,
Jul 5 2017
James is OOO. Usually I handle issues with keyboard shortcuts and the keyboard overlay, but I have no experience at all with Japanese keyboards and layout. So I wanted someone who knows about that, hence I assigned to you nona. :) This issues is probably a subset of the bigger parent Issue 300469 related to non-US keyboard layouts, for which there will be a bigger refactor of the accelerator code, but currently it's a lower priority task. Please, take a look at it and see if it's a bug that can be fixed without the need for that refactor. If you can't triage it, then toss it back to me and I'll try to find another owner.
,
Jul 5 2017
I'm sorry I no longer work on Chrome OS and my knowledge may be too old. I only know that James recently changes (or verifies) something related to these keys.
,
Jul 6 2017
Over to wuyingbing@ who has fixed this bug in R60.
,
Jul 6 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by agnescheng@chromium.org
, Jul 4 2017