it's a chromium feature, native installers are prohibited from installing an extension if it's not in the store. this is to prevent malware....

OK, so for a native addon to work, there are two parts, one the native app, one the extension.

and to be able to install the extension, it needs to be in the extension store....

I was wondering, how to do that while still in development ? Can I register an extension that is not yet finished that I can use when I create my installer ?

if I make changes to my extension, can I just upload new versions ?

usually when I make changes, it gets a new ID. will that become a different extension? or can I update the ID with new versions? do I need to await approval for every version ?

Is this described anywhere ?

please add this to the documentation page

solved wih:

"permissions": [
"nativeMessaging"
]

According to https://dev.opera.com/extensions/message-passing/ it should be possible to use runtime.sendNativeMessage.

However, when I use it, I get:

Error in eventhandler for browserAction.onClicked: TypeError: chrome.runtime.sendNativeMessage is not a function.

Is this a permissions issue? what am I doing wrong ?

chrome.runtime.sendNativeMessage("com.xxx.yyy", "get_zzz",
    function (response) {
        alert("message from external component: " + response);
    });

Hi,

The basic extension example is javascript, packaged and installed within the browser.

I recognized, accessing registry or the harddrive would be outside scope. Thus I need to create an external program.

Now, I'm wondering how to install an extension from an ordinary windows installer. Any help, or documentation appreciated.

Any examples? yet better.

thank you..

that's what I already do, but it would save the moderators work, and me some frustration. I'm surprised you haven't seen it much. It's everywhere e.g. all microsoft forums, all social media, most vbulletins etc, etc.

I have not looked it up in the RFCs but I think the second one is the correct way ( i.e. the syntax is valid ). A "duplicate key" is more like a limitation of the implementation and would not help me.

oh thank you, you may close this one.

It should either

• throw a parse error if the syntax is not valid

or if it is valid, not silently omit nodes but

• return back all nodes in correct order.