Allow users to configure keyboard shortcuts
- Edited
Something like this would be nice because every few updates, it seems that the shortcuts for certain functions get mixed all over the place with new features being added competing for shortcut dominance.
But at the same time, this is redundant and complex. And Orion is a web browser and not some programmer tool that requires thinking to reconfigure, as that would mean you should use advanced Firefox and configure it instead.
This could also fix https://orionfeedback.org/d/788-cmdz-should-only-ever-undo-text-entry, by letting the user be able to customize all shortcuts.
Okay, I guess we can just use that.
Done.
- Edited
Provide a tab within preferences detailing currently mapped shortcuts within Orion. This will benefit power users. This tab can be used to customize keyboard shortcuts. Assignments here can be linked to the ones in macOS System settings. AFAIK, no browser has implemented this, Brave have a keyboard shortcut page but its only for extensions not for the entire browser. I'm suggesting on for the browser as a whole.
I would suggest only for extension shortcuts. There are separate applications although for viewing native shortcuts, although I am thorn on whether Orion should implement it's own keyboard shortcut list perhaps in the help menu instead.
I would veto for a help menu keyboard shortcuts list instead.
Vlad Video and audio editing softwares have implemented this via the screenshots below; so i'm thinking a UI like this for a start.
At the moment, to see keyboard shortcuts for any program, I use a nifty app called Cheat Sheet that activates by holding down CMD for 3secs, interestingly this doesn't work for Orion, infact the browser freezes for a min (beachball)
These last few posts discuss the same thing here: https://orionfeedback.org/d/501-allow-users-to-configure-keyboard-shortcuts/10
I think the current approach is the perfect fit for macOS. This is how every well-behaved app should work. Why demand duplicating the same functionality that Apple already provides us?
- Edited
I agree with that sentiment. Perhaps people are not aware that this can be done?
Perhaps we can simply expose a button in preferences that opens keyboard shortcuts in OS settings?
- Edited
That would help, though if we are talking really user-friendly then to further reduce confusion it could help to have at least one shortcut pre-added for Orion under keyboard shortcuts preference pane.
This is because for someone accustomed to in-app shortcut management the process of adding a new app to system-wide keyboard shortcuts may not be obvious, at least on Monterey
But then a bit of strategically linked documentation might just resolve all of this with less effort…
+1 for using system keyboard shortcut remapping for Orion's own shortcuts. Best to use existing facilities where they exist.
However, the problem is with extensions. Not all extensions offer keyboard shortcut mapping. In Safari, the only way to map such shortcuts is laggy, complicated, and fragile UI scripting, like this:
on clickSafariToolbarButton(buttonName)
tell application "System Events"
tell application process "Safari" to tell its first window to tell toolbar 1
set theElements to UI element 1 of every group
set theElements to reverse of theElements -- working right to left
repeat with eachButton in theElements
if description of eachButton is buttonName then click eachButton
end repeat
end tell
end tell
end clickSafariToolbarButton
Something like this would also work for Orion, but its more of a workaround than a good solution.
A better solution might be where in Tools > Extensions > [name of extension >
there are menu items for Disable
and Options
, there could also be a menu item for Activate
—i.e. to react as if the extension's toolbar button was clicked (ideally, even if it is hidden in the overflow menu). This menu could then be mapped via system preferences, the same as the rest.
small_lion How would Orion know what keyboard mapping are used by an extension?
Orion wouldn’t need to know what mappings are used by extensions.
Let me give an example of what I'm talking about. The Zotero extension has one function (extract metadata from current page and save to the main Zotero application), which is activated by clicking on the extension icon. Unlike some similar extensions, it offers no way to map this to a keyboard shortcut.
I find the click-only approach to be unergonomic, especially if the extension is hidden in the overflow menu. (Sometimes I might be activating the Zotero extension 10 or 15 times in quick succession, and I suffer from RSI...) Chromium browsers offer such key mapping capability for most/all extensions. In Safari, as mentioned above, UI scripting is required.
What I am suggesting is that all that is needed for Orion is to have Tools > Extensions > [name of extension] > Activate
in the application menu for each extension, with Activate
simulating a click on the extension icon. For some extensions, this wouldn’t do anything useful, but for the likes of Zotero it would be very useful.
So, Orion wouldn’t need to know anything more about extension shortcuts than it already does. It would obviously be up to the user to avoid mapping clashes, same as with remapping any menu item.