Change key bindings (keyboard shortcuts) in Firefox Quantum
Since the quantum update all AddOns which allowed to change key bindings in Firefox seemed to have stopped working/being supported.
Is there a method to change the default key bindings in Firefox Quantum?
firefox firefox-extensions firefox-quantum
asked Nov 23 '17 at 13:07
Finn
3012311
add a comment |
Since the quantum update all AddOns which allowed to change key bindings in Firefox seemed to have stopped working/being supported.
Is there a method to change the default key bindings in Firefox Quantum?
firefox firefox-extensions firefox-quantum
asked Nov 23 '17 at 13:07
Finn
3012311
2
There is a bug for this: bugzilla.mozilla.org/show_bug.cgi?id=1303384
– andrybak
Dec 8 '17 at 22:21
add a comment |
Since the quantum update all AddOns which allowed to change key bindings in Firefox seemed to have stopped working/being supported.
Is there a method to change the default key bindings in Firefox Quantum?
firefox firefox-extensions firefox-quantum
asked Nov 23 '17 at 13:07
Finn
3012311
Since the quantum update all AddOns which allowed to change key bindings in Firefox seemed to have stopped working/being supported.
Is there a method to change the default key bindings in Firefox Quantum?
firefox firefox-extensions firefox-quantum
firefox firefox-extensions firefox-quantum
asked Nov 23 '17 at 13:07
Finn
3012311
asked Nov 23 '17 at 13:07
Finn
3012311
asked Nov 23 '17 at 13:07
Finn
3012311
asked Nov 23 '17 at 13:07
Finn
3012311
asked Nov 23 '17 at 13:07
Finn
3012311
3012311
2
There is a bug for this: bugzilla.mozilla.org/show_bug.cgi?id=1303384
– andrybak
Dec 8 '17 at 22:21
add a comment |
2
There is a bug for this: bugzilla.mozilla.org/show_bug.cgi?id=1303384
– andrybak
Dec 8 '17 at 22:21
2
2
There is a bug for this: bugzilla.mozilla.org/show_bug.cgi?id=1303384
– andrybak
Dec 8 '17 at 22:21
There is a bug for this: bugzilla.mozilla.org/show_bug.cgi?id=1303384
– andrybak
Dec 8 '17 at 22:21
add a comment |
3 Answers
3
active
oldest
votes
There is a way. It's not super official, but basically you can unpack browser/omni.ja, edit the keybindings in chrome/browser/content/browser/browser.xul, repack it, delete startup cache and it will work.
Alternatively, you can compile your own firefox and then you don't need to unpack the binary, if you consider unpacking and repacking more hacky, than building.
Another advantage of building is that you can store your modifications on top of the official sources in git and always rebase, like I do here: https://github.com/errge/gecko-dev/tree/gregzilla-patched-20181223
I advise you to first start with the binary option, because you will have working keyboard shortcuts in 20 minutes, instead of just being at the start of the mercurial clone procedure :)
Both of these methods are independent of any extensions/webextensions and will ALWAYS work, even in the location bar and even on protected pages (as you asked in the comments). So they will work better than remapping webextensions.
I have an article written up with all the details that may interest you: https://github.com/nilcons/firefox-hacks
If you have more questions, please report issues on github.
answered Dec 23 '18 at 20:45
errge
3113
3
Welcome to Super User. Without actually providing the steps one must take, there is no answer in this post. Please edit your post to include this information, including the essential content of linked material.
– Twisty Impersonator
Dec 23 '18 at 21:15
Hey, thanks you! How this will effect the updates firefox gets? Do I have to rebuilr + reinstall firefox after each update? Or can I somehow setup a different update channel so it will fetch from my travis builds for example? That way I could mostly automate the process I hope.
– Finn
Dec 27 '18 at 15:00
1
If you are just after the keybindings (and not interested in compiling your own for other reasons), then I would use this part of the article: github.com/nilcons/firefox-hacks#binary-hacking-automated So basically I have this script as "patch-the-fox" and whenever I notice that firefox is not working correctly, I just start a shell, and run "patch-the-fox" and restart. Then it's good again for 2-3 weeks.
– errge
Dec 28 '18 at 15:40
add a comment |
From Firefox support:
https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox-tasks-quickly :
Note: You can customize keyboard shortcuts for Firefox using the https://addons.mozilla.org/firefox/addon/saka-key/ extension.
I hope it is what you were looking for.
answered Dec 11 '17 at 23:15
Moreno G
113
3
Thanks, unfortunately this extension is not so practical. If it would work, this one: github.com/mikecrittenden/shortkeys would be nice. But it seems like, Firefox is allowing websites to suppress the bindings, which is super annoying when your bindings only work on a few sites :(
– Finn
Dec 18 '17 at 10:33
1
Fully agree, they need to find a good workaround to fix it
– Moreno G
Apr 28 '18 at 15:04
add a comment |
I am not sure what kind of shortcuts you are after but there is a great extensions called Vimium FF that allows you to browse completely mouseless. This extensions offers a filter mechanism that allows you to decide in which websites the keybindings should work.
It is still in experimental stage, since it is a port from a Chrome extensions but I am using and did encounter any bug or problem.
The bindings follow the VIM bindings and should be natural if you are already familiar with those, otherwise, you can custumize them to your own taste.
answered Aug 9 '18 at 21:38
Marcelo Avila
333
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%2f1271147%2fchange-key-bindings-keyboard-shortcuts-in-firefox-quantum%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is a way. It's not super official, but basically you can unpack browser/omni.ja, edit the keybindings in chrome/browser/content/browser/browser.xul, repack it, delete startup cache and it will work.
Alternatively, you can compile your own firefox and then you don't need to unpack the binary, if you consider unpacking and repacking more hacky, than building.
Another advantage of building is that you can store your modifications on top of the official sources in git and always rebase, like I do here: https://github.com/errge/gecko-dev/tree/gregzilla-patched-20181223
I advise you to first start with the binary option, because you will have working keyboard shortcuts in 20 minutes, instead of just being at the start of the mercurial clone procedure :)
Both of these methods are independent of any extensions/webextensions and will ALWAYS work, even in the location bar and even on protected pages (as you asked in the comments). So they will work better than remapping webextensions.
I have an article written up with all the details that may interest you: https://github.com/nilcons/firefox-hacks
If you have more questions, please report issues on github.
answered Dec 23 '18 at 20:45
errge
3113
3
Welcome to Super User. Without actually providing the steps one must take, there is no answer in this post. Please edit your post to include this information, including the essential content of linked material.
– Twisty Impersonator
Dec 23 '18 at 21:15
Hey, thanks you! How this will effect the updates firefox gets? Do I have to rebuilr + reinstall firefox after each update? Or can I somehow setup a different update channel so it will fetch from my travis builds for example? That way I could mostly automate the process I hope.
– Finn
Dec 27 '18 at 15:00
1
If you are just after the keybindings (and not interested in compiling your own for other reasons), then I would use this part of the article: github.com/nilcons/firefox-hacks#binary-hacking-automated So basically I have this script as "patch-the-fox" and whenever I notice that firefox is not working correctly, I just start a shell, and run "patch-the-fox" and restart. Then it's good again for 2-3 weeks.
– errge
Dec 28 '18 at 15:40
add a comment |
There is a way. It's not super official, but basically you can unpack browser/omni.ja, edit the keybindings in chrome/browser/content/browser/browser.xul, repack it, delete startup cache and it will work.
Alternatively, you can compile your own firefox and then you don't need to unpack the binary, if you consider unpacking and repacking more hacky, than building.
Another advantage of building is that you can store your modifications on top of the official sources in git and always rebase, like I do here: https://github.com/errge/gecko-dev/tree/gregzilla-patched-20181223
I advise you to first start with the binary option, because you will have working keyboard shortcuts in 20 minutes, instead of just being at the start of the mercurial clone procedure :)
Both of these methods are independent of any extensions/webextensions and will ALWAYS work, even in the location bar and even on protected pages (as you asked in the comments). So they will work better than remapping webextensions.
I have an article written up with all the details that may interest you: https://github.com/nilcons/firefox-hacks
If you have more questions, please report issues on github.
answered Dec 23 '18 at 20:45
errge
3113
3
Welcome to Super User. Without actually providing the steps one must take, there is no answer in this post. Please edit your post to include this information, including the essential content of linked material.
– Twisty Impersonator
Dec 23 '18 at 21:15
Hey, thanks you! How this will effect the updates firefox gets? Do I have to rebuilr + reinstall firefox after each update? Or can I somehow setup a different update channel so it will fetch from my travis builds for example? That way I could mostly automate the process I hope.
– Finn
Dec 27 '18 at 15:00
1
If you are just after the keybindings (and not interested in compiling your own for other reasons), then I would use this part of the article: github.com/nilcons/firefox-hacks#binary-hacking-automated So basically I have this script as "patch-the-fox" and whenever I notice that firefox is not working correctly, I just start a shell, and run "patch-the-fox" and restart. Then it's good again for 2-3 weeks.
– errge
Dec 28 '18 at 15:40
add a comment |
There is a way. It's not super official, but basically you can unpack browser/omni.ja, edit the keybindings in chrome/browser/content/browser/browser.xul, repack it, delete startup cache and it will work.
Alternatively, you can compile your own firefox and then you don't need to unpack the binary, if you consider unpacking and repacking more hacky, than building.
Another advantage of building is that you can store your modifications on top of the official sources in git and always rebase, like I do here: https://github.com/errge/gecko-dev/tree/gregzilla-patched-20181223
I advise you to first start with the binary option, because you will have working keyboard shortcuts in 20 minutes, instead of just being at the start of the mercurial clone procedure :)
Both of these methods are independent of any extensions/webextensions and will ALWAYS work, even in the location bar and even on protected pages (as you asked in the comments). So they will work better than remapping webextensions.
I have an article written up with all the details that may interest you: https://github.com/nilcons/firefox-hacks
If you have more questions, please report issues on github.
answered Dec 23 '18 at 20:45
errge
3113
There is a way. It's not super official, but basically you can unpack browser/omni.ja, edit the keybindings in chrome/browser/content/browser/browser.xul, repack it, delete startup cache and it will work.
Alternatively, you can compile your own firefox and then you don't need to unpack the binary, if you consider unpacking and repacking more hacky, than building.
Another advantage of building is that you can store your modifications on top of the official sources in git and always rebase, like I do here: https://github.com/errge/gecko-dev/tree/gregzilla-patched-20181223
I advise you to first start with the binary option, because you will have working keyboard shortcuts in 20 minutes, instead of just being at the start of the mercurial clone procedure :)
Both of these methods are independent of any extensions/webextensions and will ALWAYS work, even in the location bar and even on protected pages (as you asked in the comments). So they will work better than remapping webextensions.
I have an article written up with all the details that may interest you: https://github.com/nilcons/firefox-hacks
If you have more questions, please report issues on github.
answered Dec 23 '18 at 20:45
errge
3113
answered Dec 23 '18 at 20:45
errge
3113
answered Dec 23 '18 at 20:45
errge
3113
answered Dec 23 '18 at 20:45
errge
3113
3113
3
Welcome to Super User. Without actually providing the steps one must take, there is no answer in this post. Please edit your post to include this information, including the essential content of linked material.
– Twisty Impersonator
Dec 23 '18 at 21:15
Hey, thanks you! How this will effect the updates firefox gets? Do I have to rebuilr + reinstall firefox after each update? Or can I somehow setup a different update channel so it will fetch from my travis builds for example? That way I could mostly automate the process I hope.
– Finn
Dec 27 '18 at 15:00
1
If you are just after the keybindings (and not interested in compiling your own for other reasons), then I would use this part of the article: github.com/nilcons/firefox-hacks#binary-hacking-automated So basically I have this script as "patch-the-fox" and whenever I notice that firefox is not working correctly, I just start a shell, and run "patch-the-fox" and restart. Then it's good again for 2-3 weeks.
– errge
Dec 28 '18 at 15:40
add a comment |
3
Welcome to Super User. Without actually providing the steps one must take, there is no answer in this post. Please edit your post to include this information, including the essential content of linked material.
– Twisty Impersonator
Dec 23 '18 at 21:15
Hey, thanks you! How this will effect the updates firefox gets? Do I have to rebuilr + reinstall firefox after each update? Or can I somehow setup a different update channel so it will fetch from my travis builds for example? That way I could mostly automate the process I hope.
– Finn
Dec 27 '18 at 15:00
1
If you are just after the keybindings (and not interested in compiling your own for other reasons), then I would use this part of the article: github.com/nilcons/firefox-hacks#binary-hacking-automated So basically I have this script as "patch-the-fox" and whenever I notice that firefox is not working correctly, I just start a shell, and run "patch-the-fox" and restart. Then it's good again for 2-3 weeks.
– errge
Dec 28 '18 at 15:40
3
3
Welcome to Super User. Without actually providing the steps one must take, there is no answer in this post. Please edit your post to include this information, including the essential content of linked material.
– Twisty Impersonator
Dec 23 '18 at 21:15
Welcome to Super User. Without actually providing the steps one must take, there is no answer in this post. Please edit your post to include this information, including the essential content of linked material.
– Twisty Impersonator
Dec 23 '18 at 21:15
Hey, thanks you! How this will effect the updates firefox gets? Do I have to rebuilr + reinstall firefox after each update? Or can I somehow setup a different update channel so it will fetch from my travis builds for example? That way I could mostly automate the process I hope.
– Finn
Dec 27 '18 at 15:00
Hey, thanks you! How this will effect the updates firefox gets? Do I have to rebuilr + reinstall firefox after each update? Or can I somehow setup a different update channel so it will fetch from my travis builds for example? That way I could mostly automate the process I hope.
– Finn
Dec 27 '18 at 15:00
1
1
If you are just after the keybindings (and not interested in compiling your own for other reasons), then I would use this part of the article: github.com/nilcons/firefox-hacks#binary-hacking-automated So basically I have this script as "patch-the-fox" and whenever I notice that firefox is not working correctly, I just start a shell, and run "patch-the-fox" and restart. Then it's good again for 2-3 weeks.
– errge
Dec 28 '18 at 15:40
If you are just after the keybindings (and not interested in compiling your own for other reasons), then I would use this part of the article: github.com/nilcons/firefox-hacks#binary-hacking-automated So basically I have this script as "patch-the-fox" and whenever I notice that firefox is not working correctly, I just start a shell, and run "patch-the-fox" and restart. Then it's good again for 2-3 weeks.
– errge
Dec 28 '18 at 15:40
add a comment |
From Firefox support:
https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox-tasks-quickly :
Note: You can customize keyboard shortcuts for Firefox using the https://addons.mozilla.org/firefox/addon/saka-key/ extension.
I hope it is what you were looking for.
answered Dec 11 '17 at 23:15
Moreno G
113
3
Thanks, unfortunately this extension is not so practical. If it would work, this one: github.com/mikecrittenden/shortkeys would be nice. But it seems like, Firefox is allowing websites to suppress the bindings, which is super annoying when your bindings only work on a few sites :(
– Finn
Dec 18 '17 at 10:33
1
Fully agree, they need to find a good workaround to fix it
– Moreno G
Apr 28 '18 at 15:04
add a comment |
From Firefox support:
https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox-tasks-quickly :
Note: You can customize keyboard shortcuts for Firefox using the https://addons.mozilla.org/firefox/addon/saka-key/ extension.
I hope it is what you were looking for.
answered Dec 11 '17 at 23:15
Moreno G
113
3
Thanks, unfortunately this extension is not so practical. If it would work, this one: github.com/mikecrittenden/shortkeys would be nice. But it seems like, Firefox is allowing websites to suppress the bindings, which is super annoying when your bindings only work on a few sites :(
– Finn
Dec 18 '17 at 10:33
1
Fully agree, they need to find a good workaround to fix it
– Moreno G
Apr 28 '18 at 15:04
add a comment |
From Firefox support:
https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox-tasks-quickly :
Note: You can customize keyboard shortcuts for Firefox using the https://addons.mozilla.org/firefox/addon/saka-key/ extension.
I hope it is what you were looking for.
answered Dec 11 '17 at 23:15
Moreno G
113
From Firefox support:
https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox-tasks-quickly :
Note: You can customize keyboard shortcuts for Firefox using the https://addons.mozilla.org/firefox/addon/saka-key/ extension.
I hope it is what you were looking for.
answered Dec 11 '17 at 23:15
Moreno G
113
edited Apr 28 '18 at 15:04
answered Dec 11 '17 at 23:15
Moreno G
113
answered Dec 11 '17 at 23:15
Moreno G
113
answered Dec 11 '17 at 23:15
Moreno G
113
113
3
Thanks, unfortunately this extension is not so practical. If it would work, this one: github.com/mikecrittenden/shortkeys would be nice. But it seems like, Firefox is allowing websites to suppress the bindings, which is super annoying when your bindings only work on a few sites :(
– Finn
Dec 18 '17 at 10:33
1
Fully agree, they need to find a good workaround to fix it
– Moreno G
Apr 28 '18 at 15:04
add a comment |
3
Thanks, unfortunately this extension is not so practical. If it would work, this one: github.com/mikecrittenden/shortkeys would be nice. But it seems like, Firefox is allowing websites to suppress the bindings, which is super annoying when your bindings only work on a few sites :(
– Finn
Dec 18 '17 at 10:33
1
Fully agree, they need to find a good workaround to fix it
– Moreno G
Apr 28 '18 at 15:04
3
3
Thanks, unfortunately this extension is not so practical. If it would work, this one: github.com/mikecrittenden/shortkeys would be nice. But it seems like, Firefox is allowing websites to suppress the bindings, which is super annoying when your bindings only work on a few sites :(
– Finn
Dec 18 '17 at 10:33
Thanks, unfortunately this extension is not so practical. If it would work, this one: github.com/mikecrittenden/shortkeys would be nice. But it seems like, Firefox is allowing websites to suppress the bindings, which is super annoying when your bindings only work on a few sites :(
– Finn
Dec 18 '17 at 10:33
1
1
Fully agree, they need to find a good workaround to fix it
– Moreno G
Apr 28 '18 at 15:04
Fully agree, they need to find a good workaround to fix it
– Moreno G
Apr 28 '18 at 15:04
add a comment |
I am not sure what kind of shortcuts you are after but there is a great extensions called Vimium FF that allows you to browse completely mouseless. This extensions offers a filter mechanism that allows you to decide in which websites the keybindings should work.
It is still in experimental stage, since it is a port from a Chrome extensions but I am using and did encounter any bug or problem.
The bindings follow the VIM bindings and should be natural if you are already familiar with those, otherwise, you can custumize them to your own taste.
answered Aug 9 '18 at 21:38
Marcelo Avila
333
add a comment |
I am not sure what kind of shortcuts you are after but there is a great extensions called Vimium FF that allows you to browse completely mouseless. This extensions offers a filter mechanism that allows you to decide in which websites the keybindings should work.
It is still in experimental stage, since it is a port from a Chrome extensions but I am using and did encounter any bug or problem.
The bindings follow the VIM bindings and should be natural if you are already familiar with those, otherwise, you can custumize them to your own taste.
answered Aug 9 '18 at 21:38
Marcelo Avila
333
add a comment |
I am not sure what kind of shortcuts you are after but there is a great extensions called Vimium FF that allows you to browse completely mouseless. This extensions offers a filter mechanism that allows you to decide in which websites the keybindings should work.
It is still in experimental stage, since it is a port from a Chrome extensions but I am using and did encounter any bug or problem.
The bindings follow the VIM bindings and should be natural if you are already familiar with those, otherwise, you can custumize them to your own taste.
answered Aug 9 '18 at 21:38
Marcelo Avila
333
I am not sure what kind of shortcuts you are after but there is a great extensions called Vimium FF that allows you to browse completely mouseless. This extensions offers a filter mechanism that allows you to decide in which websites the keybindings should work.
It is still in experimental stage, since it is a port from a Chrome extensions but I am using and did encounter any bug or problem.
The bindings follow the VIM bindings and should be natural if you are already familiar with those, otherwise, you can custumize them to your own taste.
answered Aug 9 '18 at 21:38
Marcelo Avila
333
answered Aug 9 '18 at 21:38
Marcelo Avila
333
answered Aug 9 '18 at 21:38
Marcelo Avila
333
answered Aug 9 '18 at 21:38
Marcelo Avila
333
333
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1271147%2fchange-key-bindings-keyboard-shortcuts-in-firefox-quantum%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
2
There is a bug for this: bugzilla.mozilla.org/show_bug.cgi?id=1303384
– andrybak
Dec 8 '17 at 22:21