New issue
Advanced search Search tips

Issue 686997 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug
M57



Sign in to add a comment

Search-L shortcut fails to lock screen when the focus is in an input field with IME enabled

Project Member Reported by uekawa@chromium.org, Jan 31 2017

Issue description

Chrome Version:  56.0.2924.79 beta 
OS version: 9000.76.0

What steps will reproduce the problem?
(1) switch to Japanese IME
(2) ctrl-search-L to lock screen

What is the expected result?
Screen is locked

What happens instead?
'L' is entered.


Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 
Owner: shuchen@chromium.org
Status: Assigned (was: Untriaged)
Per triage: mind taking a look at this? 
Labels: -Pri-3 Pri-2
Owner: wuyingbing@chromium.org
Yingbing, can you please take a look? Thanks.

Owner: shuchen@chromium.org
Hi Shu,
The root cause is:
When user hold "search" key, then press "L".
Input API doesn't pass "search" key state, it only pass normal "L" key.
I suggest set "metaKey" as true when pass "L" keydown event.
Summary: Search-L shortcut fails to lock screen when the focus is in an input field with IME enabled (was: Japanese IME eats ctrl-search-L)
Labels: -Pri-2 Pri-1
Project Member

Comment 6 by bugdroid1@chromium.org, Feb 20 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6fbd37145e9b8eb98e1e5b330364db3fd07dd719

commit 6fbd37145e9b8eb98e1e5b330364db3fd07dd719
Author: shuchen <shuchen@chromium.org>
Date: Mon Feb 20 08:06:52 2017

Don't handle the key events with Command (Search) modifier by IME.

BUG= 686997 

Review-Url: https://codereview.chromium.org/2704993002
Cr-Commit-Position: refs/heads/master@{#451579}

[modify] https://crrev.com/6fbd37145e9b8eb98e1e5b330364db3fd07dd719/chrome/browser/ui/input_method/input_method_engine_base.cc

Labels: M57
Labels: Merge-Request-57
Project Member

Comment 9 by sheriffbot@chromium.org, Feb 21 2017

Labels: -Merge-Request-57 Hotlist-Merge-Approved Merge-Approved-57
Your change meets the bar and is auto-approved for M57. Please go ahead and merge the CL to branch 2987 manually. Please contact milestone owner if you have questions.
Owners: amineer@(clank), cmasso@(bling), ketakid@(cros), govind@(desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 10 by bugdroid1@chromium.org, Feb 21 2017

Labels: -merge-approved-57 merge-merged-2987
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d2fc4244045288217b0b05f5433747263caa8361

commit d2fc4244045288217b0b05f5433747263caa8361
Author: Shu Chen <shuchen@google.com>
Date: Tue Feb 21 11:01:36 2017

Don't handle the key events with Command (Search) modifier by IME.

BUG= 686997 

Review-Url: https://codereview.chromium.org/2704993002
Cr-Commit-Position: refs/heads/master@{#451579}
(cherry picked from commit 6fbd37145e9b8eb98e1e5b330364db3fd07dd719)

Review-Url: https://codereview.chromium.org/2708853003 .
Cr-Commit-Position: refs/branch-heads/2987@{#606}
Cr-Branched-From: ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943}

[modify] https://crrev.com/d2fc4244045288217b0b05f5433747263caa8361/chrome/browser/ui/input_method/input_method_engine_base.cc

Status: Fixed (was: Assigned)

Comment 12 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 13 by dchan@google.com, May 30 2017

Labels: VerifyIn-60
Labels: VerifyIn-61

Comment 15 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment