Chrome “Jump to Tab” shortcut broken with French Keyboard (OSX)
I've updated my OSX to Mojave yesterday, and Chrome's jump to tab function stopped working. As I have a french keyboard, my default numbers are & é " ' ( § è ! ç à, and when hitting shift, 1234567890.
When I use Cmd + Shift + Number it works, but first, a two finger shortcut is better, and second, Cmd + Shift + 3-5 is already taken for screenshots.
Before my OS Upgrade, it all worked smoothly... Chrome doesn't seem to be friend with Mojave as I find it very slow as well...
Thanks for your help!
macos google-chrome keyboard keyboard-shortcuts keyboard-layout
edited Oct 18 '18 at 7:47
Ahmed Ashour
1,3251715
asked Oct 18 '18 at 4:04
ThaiThai
261
add a comment |
I've updated my OSX to Mojave yesterday, and Chrome's jump to tab function stopped working. As I have a french keyboard, my default numbers are & é " ' ( § è ! ç à, and when hitting shift, 1234567890.
When I use Cmd + Shift + Number it works, but first, a two finger shortcut is better, and second, Cmd + Shift + 3-5 is already taken for screenshots.
Before my OS Upgrade, it all worked smoothly... Chrome doesn't seem to be friend with Mojave as I find it very slow as well...
Thanks for your help!
macos google-chrome keyboard keyboard-shortcuts keyboard-layout
edited Oct 18 '18 at 7:47
Ahmed Ashour
1,3251715
asked Oct 18 '18 at 4:04
ThaiThai
261
I have the same issue with my keyboard in the Belgian layout. It used to work with cmd + number on Mojave, but I think the Chrome 70 update broke it. Now it's cmd + shift + number.
– Matt
Oct 18 '18 at 16:28
And then if you want to go to the third tab, you take a screenshot :)
– Thai
Oct 24 '18 at 3:43
I have this issue in High Sierra. Related to Chrome.
– Benoit Duffez
Nov 12 '18 at 20:35
add a comment |
I've updated my OSX to Mojave yesterday, and Chrome's jump to tab function stopped working. As I have a french keyboard, my default numbers are & é " ' ( § è ! ç à, and when hitting shift, 1234567890.
When I use Cmd + Shift + Number it works, but first, a two finger shortcut is better, and second, Cmd + Shift + 3-5 is already taken for screenshots.
Before my OS Upgrade, it all worked smoothly... Chrome doesn't seem to be friend with Mojave as I find it very slow as well...
Thanks for your help!
macos google-chrome keyboard keyboard-shortcuts keyboard-layout
edited Oct 18 '18 at 7:47
Ahmed Ashour
1,3251715
asked Oct 18 '18 at 4:04
ThaiThai
261
I've updated my OSX to Mojave yesterday, and Chrome's jump to tab function stopped working. As I have a french keyboard, my default numbers are & é " ' ( § è ! ç à, and when hitting shift, 1234567890.
When I use Cmd + Shift + Number it works, but first, a two finger shortcut is better, and second, Cmd + Shift + 3-5 is already taken for screenshots.
Before my OS Upgrade, it all worked smoothly... Chrome doesn't seem to be friend with Mojave as I find it very slow as well...
Thanks for your help!
macos google-chrome keyboard keyboard-shortcuts keyboard-layout
macos google-chrome keyboard keyboard-shortcuts keyboard-layout
edited Oct 18 '18 at 7:47
Ahmed Ashour
1,3251715
asked Oct 18 '18 at 4:04
ThaiThai
261
edited Oct 18 '18 at 7:47
Ahmed Ashour
1,3251715
asked Oct 18 '18 at 4:04
ThaiThai
261
edited Oct 18 '18 at 7:47
Ahmed Ashour
1,3251715
edited Oct 18 '18 at 7:47
Ahmed Ashour
1,3251715
edited Oct 18 '18 at 7:47
Ahmed Ashour
1,3251715
1,3251715
asked Oct 18 '18 at 4:04
ThaiThai
261
asked Oct 18 '18 at 4:04
ThaiThai
261
asked Oct 18 '18 at 4:04
ThaiThai
261
261
I have the same issue with my keyboard in the Belgian layout. It used to work with cmd + number on Mojave, but I think the Chrome 70 update broke it. Now it's cmd + shift + number.
– Matt
Oct 18 '18 at 16:28
And then if you want to go to the third tab, you take a screenshot :)
– Thai
Oct 24 '18 at 3:43
I have this issue in High Sierra. Related to Chrome.
– Benoit Duffez
Nov 12 '18 at 20:35
add a comment |
I have the same issue with my keyboard in the Belgian layout. It used to work with cmd + number on Mojave, but I think the Chrome 70 update broke it. Now it's cmd + shift + number.
– Matt
Oct 18 '18 at 16:28
And then if you want to go to the third tab, you take a screenshot :)
– Thai
Oct 24 '18 at 3:43
I have this issue in High Sierra. Related to Chrome.
– Benoit Duffez
Nov 12 '18 at 20:35
I have the same issue with my keyboard in the Belgian layout. It used to work with cmd + number on Mojave, but I think the Chrome 70 update broke it. Now it's cmd + shift + number.
– Matt
Oct 18 '18 at 16:28
I have the same issue with my keyboard in the Belgian layout. It used to work with cmd + number on Mojave, but I think the Chrome 70 update broke it. Now it's cmd + shift + number.
– Matt
Oct 18 '18 at 16:28
And then if you want to go to the third tab, you take a screenshot :)
– Thai
Oct 24 '18 at 3:43
And then if you want to go to the third tab, you take a screenshot :)
– Thai
Oct 24 '18 at 3:43
I have this issue in High Sierra. Related to Chrome.
– Benoit Duffez
Nov 12 '18 at 20:35
I have this issue in High Sierra. Related to Chrome.
– Benoit Duffez
Nov 12 '18 at 20:35
add a comment |
4 Answers
4
active
oldest
votes
Looks like we'll have to wait a few more weeks:
There's a patch in review at https://chromium-review.googlesource.com/c/chromium/src/+/1372349 , once that is in the fix should in in Canary on the next day. It'll likely be on stable in chrome 73.
For now, I'm using BetterTouchTool to reassign the 10 missing keyboard shortcuts in Chrome only:
answered Jan 16 at 9:43
Nico PratNico Prat
1112
So, hopefully, this will be fixed before you need to pay for that software? :-)
– fixer1234
Jan 16 at 10:07
Fix will be shipped in Chrome 73, currently we're at 71. But I highly recommend paying for it though, it's very useful! ;)
– Nico Prat
Jan 18 at 11:24
add a comment |
I don't actually know a way round this, but the "problem" is that with a French keyboard you need to press Shift to get the numbers at all times.
All [most?] other languages don't work this way.
It might be worth experimenting with the other types of French keyboard input - there are a few - & see if one of those will do a better job for you.
answered Oct 18 '18 at 7:12
TetsujinTetsujin
15.8k53362
Well yes, but for some reason, before the update, CMD+é worked as CMD+2 in chrome... now it doesn't anymore.
– Thai
Oct 22 '18 at 9:40
add a comment |
If you are comfortable with JavaScript programming, you could use the extensions
Violentmonkey
together with
VM.registerShortcut.
Violentmonkey can inject into the displayed page a JavaScript userscript.
VM.registerShortcut can intercept entered shortcuts and translate them
to calls of JavaScript functions.
Using both of them enables the mapping of any shortcut to a JavaScript function
call.
For implementing Chrome's "Jump to Tab",
you would be using the
chrome.tabs API
to interact with the browser's tab system where you may do anything
that you like.
For example, to change the current tab you would do :
chrome.tabs.update(tabId, { highlighted: true });
Lots of additional information about the subject can be found on the Web.
answered Oct 24 '18 at 15:36
harrymcharrymc
260k14271575
add a comment |
It looks like it's a bug in the new release, check out this issue.
answered Nov 4 '18 at 18:57
kevinkevin
7542610
precisely that! indeed worked with Chrome 69, hence the suggestion to back version and stop auto update. Thanks for the heads up, will keep an eye!
– Thai
Nov 6 '18 at 2:33
Looks like it is fixed bugs.chromium.org/p/chromium/issues/detail?id=898638
– kevin
Nov 7 '18 at 11:27
Updated to Version 70.0.3538.102 - no change...
– Thai
Nov 12 '18 at 3:37
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1367785%2fchrome-jump-to-tab-shortcut-broken-with-french-keyboard-osx%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Looks like we'll have to wait a few more weeks:
There's a patch in review at https://chromium-review.googlesource.com/c/chromium/src/+/1372349 , once that is in the fix should in in Canary on the next day. It'll likely be on stable in chrome 73.
For now, I'm using BetterTouchTool to reassign the 10 missing keyboard shortcuts in Chrome only:
answered Jan 16 at 9:43
Nico PratNico Prat
1112
So, hopefully, this will be fixed before you need to pay for that software? :-)
– fixer1234
Jan 16 at 10:07
Fix will be shipped in Chrome 73, currently we're at 71. But I highly recommend paying for it though, it's very useful! ;)
– Nico Prat
Jan 18 at 11:24
add a comment |
Looks like we'll have to wait a few more weeks:
There's a patch in review at https://chromium-review.googlesource.com/c/chromium/src/+/1372349 , once that is in the fix should in in Canary on the next day. It'll likely be on stable in chrome 73.
For now, I'm using BetterTouchTool to reassign the 10 missing keyboard shortcuts in Chrome only:
answered Jan 16 at 9:43
Nico PratNico Prat
1112
So, hopefully, this will be fixed before you need to pay for that software? :-)
– fixer1234
Jan 16 at 10:07
Fix will be shipped in Chrome 73, currently we're at 71. But I highly recommend paying for it though, it's very useful! ;)
– Nico Prat
Jan 18 at 11:24
add a comment |
Looks like we'll have to wait a few more weeks:
There's a patch in review at https://chromium-review.googlesource.com/c/chromium/src/+/1372349 , once that is in the fix should in in Canary on the next day. It'll likely be on stable in chrome 73.
For now, I'm using BetterTouchTool to reassign the 10 missing keyboard shortcuts in Chrome only:
answered Jan 16 at 9:43
Nico PratNico Prat
1112
Looks like we'll have to wait a few more weeks:
There's a patch in review at https://chromium-review.googlesource.com/c/chromium/src/+/1372349 , once that is in the fix should in in Canary on the next day. It'll likely be on stable in chrome 73.
For now, I'm using BetterTouchTool to reassign the 10 missing keyboard shortcuts in Chrome only:
answered Jan 16 at 9:43
Nico PratNico Prat
1112
answered Jan 16 at 9:43
Nico PratNico Prat
1112
answered Jan 16 at 9:43
Nico PratNico Prat
1112
answered Jan 16 at 9:43
Nico PratNico Prat
1112
1112
So, hopefully, this will be fixed before you need to pay for that software? :-)
– fixer1234
Jan 16 at 10:07
Fix will be shipped in Chrome 73, currently we're at 71. But I highly recommend paying for it though, it's very useful! ;)
– Nico Prat
Jan 18 at 11:24
add a comment |
So, hopefully, this will be fixed before you need to pay for that software? :-)
– fixer1234
Jan 16 at 10:07
Fix will be shipped in Chrome 73, currently we're at 71. But I highly recommend paying for it though, it's very useful! ;)
– Nico Prat
Jan 18 at 11:24
So, hopefully, this will be fixed before you need to pay for that software? :-)
– fixer1234
Jan 16 at 10:07
So, hopefully, this will be fixed before you need to pay for that software? :-)
– fixer1234
Jan 16 at 10:07
Fix will be shipped in Chrome 73, currently we're at 71. But I highly recommend paying for it though, it's very useful! ;)
– Nico Prat
Jan 18 at 11:24
Fix will be shipped in Chrome 73, currently we're at 71. But I highly recommend paying for it though, it's very useful! ;)
– Nico Prat
Jan 18 at 11:24
add a comment |
I don't actually know a way round this, but the "problem" is that with a French keyboard you need to press Shift to get the numbers at all times.
All [most?] other languages don't work this way.
It might be worth experimenting with the other types of French keyboard input - there are a few - & see if one of those will do a better job for you.
answered Oct 18 '18 at 7:12
TetsujinTetsujin
15.8k53362
Well yes, but for some reason, before the update, CMD+é worked as CMD+2 in chrome... now it doesn't anymore.
– Thai
Oct 22 '18 at 9:40
add a comment |
I don't actually know a way round this, but the "problem" is that with a French keyboard you need to press Shift to get the numbers at all times.
All [most?] other languages don't work this way.
It might be worth experimenting with the other types of French keyboard input - there are a few - & see if one of those will do a better job for you.
answered Oct 18 '18 at 7:12
TetsujinTetsujin
15.8k53362
Well yes, but for some reason, before the update, CMD+é worked as CMD+2 in chrome... now it doesn't anymore.
– Thai
Oct 22 '18 at 9:40
add a comment |
I don't actually know a way round this, but the "problem" is that with a French keyboard you need to press Shift to get the numbers at all times.
All [most?] other languages don't work this way.
It might be worth experimenting with the other types of French keyboard input - there are a few - & see if one of those will do a better job for you.
answered Oct 18 '18 at 7:12
TetsujinTetsujin
15.8k53362
I don't actually know a way round this, but the "problem" is that with a French keyboard you need to press Shift to get the numbers at all times.
All [most?] other languages don't work this way.
It might be worth experimenting with the other types of French keyboard input - there are a few - & see if one of those will do a better job for you.
answered Oct 18 '18 at 7:12
TetsujinTetsujin
15.8k53362
answered Oct 18 '18 at 7:12
TetsujinTetsujin
15.8k53362
answered Oct 18 '18 at 7:12
TetsujinTetsujin
15.8k53362
answered Oct 18 '18 at 7:12
TetsujinTetsujin
15.8k53362
15.8k53362
Well yes, but for some reason, before the update, CMD+é worked as CMD+2 in chrome... now it doesn't anymore.
– Thai
Oct 22 '18 at 9:40
add a comment |
Well yes, but for some reason, before the update, CMD+é worked as CMD+2 in chrome... now it doesn't anymore.
– Thai
Oct 22 '18 at 9:40
Well yes, but for some reason, before the update, CMD+é worked as CMD+2 in chrome... now it doesn't anymore.
– Thai
Oct 22 '18 at 9:40
Well yes, but for some reason, before the update, CMD+é worked as CMD+2 in chrome... now it doesn't anymore.
– Thai
Oct 22 '18 at 9:40
add a comment |
If you are comfortable with JavaScript programming, you could use the extensions
Violentmonkey
together with
VM.registerShortcut.
Violentmonkey can inject into the displayed page a JavaScript userscript.
VM.registerShortcut can intercept entered shortcuts and translate them
to calls of JavaScript functions.
Using both of them enables the mapping of any shortcut to a JavaScript function
call.
For implementing Chrome's "Jump to Tab",
you would be using the
chrome.tabs API
to interact with the browser's tab system where you may do anything
that you like.
For example, to change the current tab you would do :
chrome.tabs.update(tabId, { highlighted: true });
Lots of additional information about the subject can be found on the Web.
answered Oct 24 '18 at 15:36
harrymcharrymc
260k14271575
add a comment |
If you are comfortable with JavaScript programming, you could use the extensions
Violentmonkey
together with
VM.registerShortcut.
Violentmonkey can inject into the displayed page a JavaScript userscript.
VM.registerShortcut can intercept entered shortcuts and translate them
to calls of JavaScript functions.
Using both of them enables the mapping of any shortcut to a JavaScript function
call.
For implementing Chrome's "Jump to Tab",
you would be using the
chrome.tabs API
to interact with the browser's tab system where you may do anything
that you like.
For example, to change the current tab you would do :
chrome.tabs.update(tabId, { highlighted: true });
Lots of additional information about the subject can be found on the Web.
answered Oct 24 '18 at 15:36
harrymcharrymc
260k14271575
add a comment |
If you are comfortable with JavaScript programming, you could use the extensions
Violentmonkey
together with
VM.registerShortcut.
Violentmonkey can inject into the displayed page a JavaScript userscript.
VM.registerShortcut can intercept entered shortcuts and translate them
to calls of JavaScript functions.
Using both of them enables the mapping of any shortcut to a JavaScript function
call.
For implementing Chrome's "Jump to Tab",
you would be using the
chrome.tabs API
to interact with the browser's tab system where you may do anything
that you like.
For example, to change the current tab you would do :
chrome.tabs.update(tabId, { highlighted: true });
Lots of additional information about the subject can be found on the Web.
answered Oct 24 '18 at 15:36
harrymcharrymc
260k14271575
If you are comfortable with JavaScript programming, you could use the extensions
Violentmonkey
together with
VM.registerShortcut.
Violentmonkey can inject into the displayed page a JavaScript userscript.
VM.registerShortcut can intercept entered shortcuts and translate them
to calls of JavaScript functions.
Using both of them enables the mapping of any shortcut to a JavaScript function
call.
For implementing Chrome's "Jump to Tab",
you would be using the
chrome.tabs API
to interact with the browser's tab system where you may do anything
that you like.
For example, to change the current tab you would do :
chrome.tabs.update(tabId, { highlighted: true });
Lots of additional information about the subject can be found on the Web.
answered Oct 24 '18 at 15:36
harrymcharrymc
260k14271575
answered Oct 24 '18 at 15:36
harrymcharrymc
260k14271575
answered Oct 24 '18 at 15:36
harrymcharrymc
260k14271575
answered Oct 24 '18 at 15:36
harrymcharrymc
260k14271575
260k14271575
add a comment |
add a comment |
It looks like it's a bug in the new release, check out this issue.
answered Nov 4 '18 at 18:57
kevinkevin
7542610
precisely that! indeed worked with Chrome 69, hence the suggestion to back version and stop auto update. Thanks for the heads up, will keep an eye!
– Thai
Nov 6 '18 at 2:33
Looks like it is fixed bugs.chromium.org/p/chromium/issues/detail?id=898638
– kevin
Nov 7 '18 at 11:27
Updated to Version 70.0.3538.102 - no change...
– Thai
Nov 12 '18 at 3:37
add a comment |
It looks like it's a bug in the new release, check out this issue.
answered Nov 4 '18 at 18:57
kevinkevin
7542610
precisely that! indeed worked with Chrome 69, hence the suggestion to back version and stop auto update. Thanks for the heads up, will keep an eye!
– Thai
Nov 6 '18 at 2:33
Looks like it is fixed bugs.chromium.org/p/chromium/issues/detail?id=898638
– kevin
Nov 7 '18 at 11:27
Updated to Version 70.0.3538.102 - no change...
– Thai
Nov 12 '18 at 3:37
add a comment |
It looks like it's a bug in the new release, check out this issue.
answered Nov 4 '18 at 18:57
kevinkevin
7542610
It looks like it's a bug in the new release, check out this issue.
answered Nov 4 '18 at 18:57
kevinkevin
7542610
answered Nov 4 '18 at 18:57
kevinkevin
7542610
answered Nov 4 '18 at 18:57
kevinkevin
7542610
answered Nov 4 '18 at 18:57
kevinkevin
7542610
7542610
precisely that! indeed worked with Chrome 69, hence the suggestion to back version and stop auto update. Thanks for the heads up, will keep an eye!
– Thai
Nov 6 '18 at 2:33
Looks like it is fixed bugs.chromium.org/p/chromium/issues/detail?id=898638
– kevin
Nov 7 '18 at 11:27
Updated to Version 70.0.3538.102 - no change...
– Thai
Nov 12 '18 at 3:37
add a comment |
precisely that! indeed worked with Chrome 69, hence the suggestion to back version and stop auto update. Thanks for the heads up, will keep an eye!
– Thai
Nov 6 '18 at 2:33
Looks like it is fixed bugs.chromium.org/p/chromium/issues/detail?id=898638
– kevin
Nov 7 '18 at 11:27
Updated to Version 70.0.3538.102 - no change...
– Thai
Nov 12 '18 at 3:37
precisely that! indeed worked with Chrome 69, hence the suggestion to back version and stop auto update. Thanks for the heads up, will keep an eye!
– Thai
Nov 6 '18 at 2:33
precisely that! indeed worked with Chrome 69, hence the suggestion to back version and stop auto update. Thanks for the heads up, will keep an eye!
– Thai
Nov 6 '18 at 2:33
Looks like it is fixed bugs.chromium.org/p/chromium/issues/detail?id=898638
– kevin
Nov 7 '18 at 11:27
Looks like it is fixed bugs.chromium.org/p/chromium/issues/detail?id=898638
– kevin
Nov 7 '18 at 11:27
Updated to Version 70.0.3538.102 - no change...
– Thai
Nov 12 '18 at 3:37
Updated to Version 70.0.3538.102 - no change...
– Thai
Nov 12 '18 at 3:37
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1367785%2fchrome-jump-to-tab-shortcut-broken-with-french-keyboard-osx%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I have the same issue with my keyboard in the Belgian layout. It used to work with cmd + number on Mojave, but I think the Chrome 70 update broke it. Now it's cmd + shift + number.
– Matt
Oct 18 '18 at 16:28
And then if you want to go to the third tab, you take a screenshot :)
– Thai
Oct 24 '18 at 3:43
I have this issue in High Sierra. Related to Chrome.
– Benoit Duffez
Nov 12 '18 at 20:35