There is no way to make such shortcuts. FF already have defaults and those don't change. Only other way is by Addons if they have one that does that.

Evidently you can do that with autoconfig. You will need to remove the blank space in the second link.

https://support.mozilla.org/en-US/kb/customizing-firefox-using-autoconfig https://www.reddit. com/r/firefox/comments/kilmm2/restore_ctrlshiftb_library_by_setting_configjs/

Thanks for your response, @terry. However, this is too complicated for me. I just hope firefox plays nicely with MacOS and allows us to modify shortcuts like you would usually do.

Thanks, Naman

Thanks for your response, @terry. However, this is too complicated for me. I just hope firefox plays nicely with MacOS and allows us to modify shortcuts like you would usually do. Thanks, Naman

I doubt this will happen beyond the about:config options. This is for consistency across platforms otherwise they have so many iterations of the Browser for each system it wouldn't be benefit to the Browser itself. Also remember Mozilla is a non-paid non-profit organization unlike Edge(MS) and Chrome(Google) whom can invest many more then Mozilla can to do to customize their Browser.

I also wish Firefox had a tool to change the built-in keyboard shortcuts. Although support would be more difficult...

Is the problem that Mac OS isn't able to intercept those keys after you assign them new functions at the system level, or that is working, but now you need other methods to call up those actions in Firefox?

Evidently you can do that with autoconfig. You will need to remove the blank space in the second link. https://support.mozilla.org/en-US/kb/customizing-firefox-using-autoconfig https://www.reddit. com/r/firefox/comments/kilmm2/restore_ctrlshiftb_library_by_setting_configjs/

Or my page here: https://www.userchrome.org/what-is-userchrome-js.html

I didn't mention your page because each source used a different name for the file and I thought two different names was enough.

I didn't mention your page because each source used a different name for the file and I thought two different names was enough.

No worries.