Account confirmers, Anti-spam team, Bureaucrats, canmove, Confirmed users, Module owners and peers, smwadministrator, smwcurator, Administrators, MozillaWiki team, Widget editors
7,298
edits
WebExtensions/Native Messaging: Difference between revisions
Jump to navigation
Jump to search
Changed path for manifest for Linux / User from "/.mozilla/NativeMessagingHosts" to "/.mozilla/native-messaging-hosts" ref message from jonny at pluckeye
(updated manifest locations) |
(Changed path for manifest for Linux / User from "/.mozilla/NativeMessagingHosts" to "/.mozilla/native-messaging-hosts" ref message from jonny at pluckeye) |
||
| Line 67: | Line 67: | ||
|Linux | |Linux | ||
|User | |User | ||
|<tt>~/.mozilla/ | |<tt>~/.mozilla/native-messaging-hosts/<name>.json</tt> | ||
|} | |} | ||
In the longer term, it would be valuable have a standardized approach to native messaging that works across browsers without any changes. The appropriate place to design a cross-browser standard is the [https://www.w3.org/community/browserext/ W3C browserext working group]. At the least, designing a cross-browser standard for native messaging would require designing a cross-browser standard for extension identifiers, to be used for permissions checks. This is a laudable goal, but one that is likely to some time. This leaves us with a choice between waiting for that standard implementing the above proposal right now and then adding support for the new standard when it emerges while remaining compatible with the Firefox-specific specification. The latter is obviously undesirable but not so much that it warrants holding this feature. | In the longer term, it would be valuable have a standardized approach to native messaging that works across browsers without any changes. The appropriate place to design a cross-browser standard is the [https://www.w3.org/community/browserext/ W3C browserext working group]. At the least, designing a cross-browser standard for native messaging would require designing a cross-browser standard for extension identifiers, to be used for permissions checks. This is a laudable goal, but one that is likely to some time. This leaves us with a choice between waiting for that standard implementing the above proposal right now and then adding support for the new standard when it emerges while remaining compatible with the Firefox-specific specification. The latter is obviously undesirable but not so much that it warrants holding this feature. | ||