Anyone hooked a Clarion DLL into Javascript using JS-Ctypes?

Anyone hooked a Clarion DLL into Javascript using JS-Ctypes?

https://wiki.mozilla.org/Jsctypes/api

Wondered if there’s any gotcha’s?

Its to extend some browser extensions I’m creating at the moment.

Biggest issue I can see is when a Browser is running in a sandbox, but I’m hoping to find a way to punch out of any sandbox, probably by redirecting to a local nettalk server running outside of the sandbox.

Edit.
I would imagine I will also need to include things like this into my dll to help it get loaded properly.

TIA

Edit2.

Scrap that. Google walk through from repeated searchs has thrown up this blog stating js-ctypes will be blocked and to use the new native messaging which uses json format.

Each message is serialized using JSON, UTF-8 encoded and is preceded with an unsigned 32-bit value containing the message length in native byte order.

The maximum size of a single message from the application is 1 MB. The maximum size of a message sent to the application is 4 GB.

Several years back, Roboform had a chrome extension that hooked into their windows app. No idea whether it was Win32 or not, but it was not a fun time for them, especially when they had users that synched settings across devices (and OS’s).

Not sure if this is still an issue for them, but certainly a whole set of headaches to consider.

At the time, they had their users switch to a dumbed down version of their extension that didn’t depend on the windows code.

Looking at the api’s and events available, its possible different default shipping extensions were running in different stack orders, looking at this link.
https://support.google.com/chrome/thread/28146474/roboform-overriding-chrome-autofill?hl=en

Roboform support acknowledge that chrome autofill no longer works when Roboform extension is enabled.

They blame google for disabling autofill when external password manager extension is active.

This is a problem with multiple extensions that use the same api’s/events, but its something Firefox and other browsers need to handle if its still an issue today, ie the loading order of extensions need to determine the order data is passed to api’s/events, that way the default shipping extensions would be first or second to process the data before it got to the user installed extensions.

I know this problem exists with Firefox messaging, so its possible this issue hasnt been addressed yet based on MDN (Mozilla’s API/Event documention).