+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.