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.