erikchen@ could this be related to the recent hotkey changes?

This is likely related to the MacViews transition. The Views implementation cannot deal with custom user shortcuts [or dynamic shortcuts].

Would it be correct to dupe this into issue 890418? Can't tell if the root cause is the same

I expect this is the same issue, but can't tell without further investigation.

Thanks a lot for reacting so fast! I am glad that this has received attention.

Let me know if I can be of any help testing on my machine!

Tried testing the issue on reported chrome version #71.0.3578.98 using Mac OS 10.13.6 High Sierra by following below steps.

Steps:
=====
1.Launched chrome.
2.Navigated to System Preferences -> Keyboard Shortcuts -> Mission Control.
3.Changed setting "Move left a space" to Command + left and "Move right a space" to Command + right.
4.Opened chrome.
5.Navigated to "google.com".
6.Searched a word in the search box.
7.Tried Command + left to move left and Command + right to move right.
8.Observed that in both cases it did not move to left or right on very first attempt(i.e before 10 secs).
9.Tried Command+Shift+left/right observed that it did not move to start or end of line(i.e before 10 secs).

Attached screencast for reference.
@reporter: Could you please review attached screencast and let us know if anything is being missed here. Request you to confirm if this is the issue you re pointing to.
Thanks.!

Deleted: 916123.mp4 2.3 MB

	916123.mp4 2.3 MB View Download

Thanks a lot for moving forward on this! Sorry for the slow reply, I didn't receive a notification.

It seems that you got it, except that:

- I don't have a problem with command + left or command + right. In my case they always move left a space and right a space. It might be that they didn't do anything for you if you didn't add more than 1 Space
- I usually don't have the issue with command + shift + left/right before a few seconds. I don't know why for you the issue was there from the start, but yes that's the problem I am facing. The reason why it fails from the start for you might be because Chrome was already running? If you had quit it and restarted it it might have worked for a few seconds.

Thank you for providing more feedback. Adding the requester to the cc list.

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

I'm going to go ahead and move this to available to get it out of the triage queue. This seems like a real bug, but will require someone to take the time to really investigate.

Able to reproduce the issue on chrome version #60.0.3112.113, reported chrome version #71.0.3578.98 and latest chrome #73.0.3666.0 using Mac OS 10.13.6 High Sierra by following the steps as per comment#0. 

Leaving the status as "Available" as this is confirmed by the dev, adding appropriate Target and FoundIn labels accordingly and removing Needs-Bisect label.
Thanks.!

Awesome!

I should add that I have tested on some colleagues' laptops, and while they have the exact same version of macOS, and Chrome, some had this bug and some didn't. I couldn't identify what was the difference in their settings.

I just noticed another detail. If I:
- quit Chrome completely,
- turn off macOS Switch Spaces shortcuts,
- start Chrome
- turn macOS Switch Spaces shortcuts back on, still with cmd+left/right

Then the bug doesn't seem to appear, cmd+shift+left/right work as normal in Chrome.

I just noticed it, I'll use it the whole day and I'll confirm tomorrow.

I had already noticed it in Slack, so it seems to be the same behavior.