New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 726830 link

Starred by 4 users
Status: Verified
Owner: ----
Closed: Jun 2017
Cc:
█ moshayedi@chromium.org
mkarkada@chromium.org
dhadd...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

Rebinding Search, Ctrl, etc. stopped working

Project Member Reported by rjshade@google.com, May 26 2017 
Chrome Version       : 60.0.3107.0
OS Version: 9582.0.0
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5:
  Firefox 4.x:
     IE 7/8/9:

What steps will reproduce the problem?
1. Open Settings -> Keyboard
2. Set Search to act as Ctrl
3. Press Search button

What is the expected result?
Nothing (it should be interpreted as Ctrl which does nothing on its own)

What happens instead of that?
The default Search behavior: the search window appears


This is a regression, it was working fine (I switch behavior of Search and Ctrl) until a few days ago when I restarted and updated ChromeOS.



Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (X11; CrOS x86_64 9582.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3107.0 Safari/537.36

Comment 1 by inbounds...@gmail.com, May 28 2017 

Confirmed regression on samus.

Recent update (48+hrs ago) caused the re-mapping to cease functioning. I have attempted to map/re-map and reboot between, but no permutation leads to keys being re-mapped.

Since I CTRL key swap for tmux, this is killing my chromebooks usability.

Version 60.0.3107.0 dev (64-bit)
Platform 9582.0.0 (Official Build) dev-channel samus
ARC Version 4030420
Firmware Google_Samus.6300.174.0

Comment 2 by rohi...@chromium.org, Jun 3 2017

Components: UI>Input>KeyboardShortcuts

Comment 3 by rohi...@chromium.org, Jun 3 2017

Labels: -Pri-3 Pri-2

Comment 4 by k...@chromium.org, Jun 3 2017 

I'm seeing it as well. Quite crippling.

Version  60.0.3112.10 (Official Build) dev (64-bit)
Platform 9592.3.0 (Official Build) dev-channel celes
Firmware Google_Celes.7287.92.74
ARC      4046673

Comment 5 by tsergeant@chromium.org, Jun 5 2017

Cc: moshayedi@chromium.org
Labels: M-60
Status: Fixed (was: Unconfirmed)
I've just spent a little while investigating this, since I was finding it quite frustrating.

The original culprit CL was R472941. This CL also seemed to cause some problems with Talkback/ChromeVox, tracked in  issue 727179 . The root cause was fixed in R476848, so this should roll through to ChromeOS Dev channel eventually.

Everything seems under control, so I'm marking this issue as fixed.

Comment 6 by rjshade@google.com, Jun 8 2017 

tsergeant: thanks for the update. Do you know when Dev is expected to get the fix?

Comment 7 by tsergeant@chromium.org, Jun 8 2017 

Looks like the fix didn't quite make it into the latest dev channel release (60.0.3112.20), so it will probably roll through next week.

Comment 8 by mkarkada@chromium.org, Aug 1 2017

Cc: mkarkada@chromium.org dhadd...@chromium.org
Status: Verified (was: Fixed)
Verified on Chrome OS 9592.71.0, 60.0.3112.80 (dev build).
►

Sign in to add a comment