rearrange-tabs: Chrome 69 address bar bug

Highlight address bar.

Alt/Option + Shift + <-- should do word selection stuff. Instead it now shifts tabs around.

Thanks for helpful extension. I use it all the time.

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 22
  • Comments: 17 (8 by maintainers)

Most upvoted comments

This is not a fix, but for some reason, changing the second dropdown from “In Chrome” to “Global” solves the address bar issue.

@corysimmons I’ve noticed this just now. Thanks for raising this issue. It seems like something around the shortcuts changed in Chrome 69. The only thing I can currently think of is that Chrome probably has started considering the default key from the manifest.json file. That’s the only place Alt+Shift+<arrow> key combination is used (for Mac). I’ll try removing it and test it locally and test it. If that works, I’ll ship it out as soon as I can. Once again, thanks for raising the issue and I’m glad you find the extension helpful. Cheers!

Add those shortcuts and add a place in the extension to change the shortcut to whatever the user wants. In that area, link to this issue.

If anyone complains, carve their heart out with a spoon.

I’ve reached out to Chrome Dev team and I haven’t received any response back.

During debugging and testing, I tried switching the shortcut keys for Mac from <kbd>Ctrl+Shift+Left/Right/Up/Down</kbd> to <kbd>Ctrl+CMD+Left/Right/Up/Down</kbd>. This worked like a charm.

Pros

  • This will fix the issue and since <kbd>Ctrl+CMD+Left/Right/Up/Down</kbd> is not used for editing text

Cons

  • Besides the fact that this will break the extension for the existing users, the existing users will also have to get used to the new shortcuts.

So, I’m trying to decide if the change is worth it.

Appreciate the feedback, @corysimmons!

I think I’ll add a pop-up or something similar that shows up once the extension is updated. That way it’d be easier to let the existing users know of the change.

+1 Love this extension, btw

Still having this issue on OSX. I love this extension but can’t use it with this bug.