Support for Orion browser in "Front Browser" actions and variables

[kevinb]

@peternlewis

It's not really about using WebKit so much as it is about the details of it's AppleScript dictionary.

Ah yes, of course.

@peternlewis

It is the handling of document/window/etc that makes the difference in the AppleScript being compatible or not compatible.

I can confirm that, in your second example, replacing "com.apple.Safari" with "com.kagi.kagimacOS" works.This is not the case when applied to the first script. Modifying my original examples to use application id in place of application also works, so it all seems consistent.

@peternlewis

If it is compatible with Chrome, you can just add it as a Chrome browser, you can add it as an additional browser with the AdditionalWebBrowserBundleIDs setting.

If it is compatible with Safari, then it would need an additional change to the engine as currently any compatible browser is assumed to be Chrome-compatible unless it has “safari” in the bundle id somewhere.

As an additional experiment, I have just tried the following, and then restarted KM (editor and engine):
defaults write com.stairways.keyboardmaestro.engine AppleScriptSafariBundleID -string "com.kagi.kagimacOS"
and
defaults write com.stairways.keyboardmaestro.engine BrowserSafariName -string "com.kagi.kagimacOS"

%SafariURL% then gave the URL from Orion, but %SafariTitle% was empty.