Re: [EXTERNAL] - Re: Java plugin phase out timeline

This is not the right list for this question: it should be asked on the
[email protected] mailing list. However I will give you a link to the
documentation which includes a specific warning about this behavior:
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Native_messaging#Closing_the_native_app

--BDS


On Wed, Apr 12, 2017 at 1:40 PM, Peter Weinstein <[email protected]>
wrote:

> Hi
>
>
>
> I'm looking for Webextensions help.
>
>
>
>
>
> I have a Webextension which launches a native app using
>
> the chrome.runtime.sendNativeMessage(...) API.
>
>
>
> This extension normally invokes an already running process to get some
>
> work done; noramlly the end result is to download a document from a
>
> server and start a Microsoft Office Application (e.g. WinWord.exe) to
>
> edit/review.
>
>
>
> The extension returns immediately.
>
>
>
> However, there is a problem. If the long-running application is not
>
> actually running, then it is started. But when the extension gets a
>
> response message, it kills the native application, and every process
>
> created by it.
>
>
>
> This is unexpected (by me); Chrome behavior differs.
>
>
>
> Is this expected behavior by you? Is it documented? Is there a
>
> mechanism for my native application to launch a task which continues
>
> to run after the native application has returned to Firefox, and
>
> exited?
>
>
> _______________________________________________
> dev-tech-plugins mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-tech-plugins
>