Sami Vänttinen

@vyashole I haven't tried it out yet, but seems strange if `nativeMessaging` gives a warning because it should be supported.

Lets see how this goes. (Haven't tried the custom browser option yet as Safari is not supported in the current KeePassXC release). EDIT: I need to inspect the sample code...

> See: https://developer.apple.com/documentation/safariservices/safari_web_extensions/messaging_between_the_app_and_javascript_in_a_safari_web_extension > > > Safari ignores the `application.id` parameter and only sends the message to the containing macOS app’s native app extension. > > This means the safari...

@vyashole I have problems compiling the code (event the example one, Native Messaging Demo Extension). Even when I already have latest Catalina, XCode 12 and Safari 14, the code gives...

I've been looking at the possible implementation and it seems the best solution for this is to wrap an own application for macOS that contains the extension + the Safari...

> They always gotta be special.... Indeed. I almost thought this thing would be easy to do. Basically we have to write an own "proxy" application that works only with...

Luckily the XCode project loads the extension source files as references so there's no need to copy files around.

@OsapBender Cannot promise anything yet. I have some troubles sending messages from extension to the application. And I haven't had time to do or test it any further.

@joconcepts Not yet. But we haven't forgotten this one.

@joconcepts No. We are waiting for feedback from Apple for a certain issue.