forked from mdn/content
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove Page macro from native messaging doc (mdn#5230)
- Loading branch information
1 parent
257a85b
commit fac4ed4
Showing
1 changed file
with
6 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,7 +6,7 @@ | |
--- | ||
<div>{{AddonSidebar}}</div> | ||
|
||
<p><span class="seoSummary"><strong>Native messaging</strong> enables an extension to exchange messages with a native application, installed on the user's computer. The native messaging serves the extensions without additional accesses over the web. </span></p> | ||
<p><strong>Native messaging</strong> enables an extension to exchange messages with a native application, installed on the user's computer. The native messaging serves the extensions without additional accesses over the web.</p> | ||
|
||
<p>Password managers: The native application manages, stores, and encrypts passwords. Then the native application communicates with the extension to populate web forms.</p> | ||
|
||
|
@@ -72,7 +72,7 @@ <h3 id="Extension_manifest">Extension manifest</h3> | |
}</pre> | ||
|
||
<div class="notecard note"> | ||
<p><strong>Note:</strong> Chrome does not support the <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/browser_specific_settings">browser_specific_settings</a> key. You will need to use another manifest without this key to install an equivalent WebExtension on Chrome. See <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_messaging#chrome_incompatibilities">Chrome incompatibilities below</a>.</p> | ||
<p><strong>Note:</strong> Chrome does not support the <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/browser_specific_settings">browser_specific_settings</a> key. You will need to use another manifest without this key to install an equivalent WebExtension on Chrome. See <a href="#chrome_incompatibilities">Chrome incompatibilities below</a>.</p> | ||
</div> | ||
|
||
<h3 id="App_manifest">App manifest</h3> | ||
|
@@ -96,7 +96,7 @@ <h3 id="App_manifest">App manifest</h3> | |
<p>This allows the extension whose ID is <code>"[email protected]"</code> to connect, by passing the name <code>"ping_pong"</code> into the relevant {{WebExtAPIRef("runtime")}} API function. The application itself is at <code>"/path/to/native-messaging/app/ping_pong.py"</code>.</p> | ||
|
||
<div class="notecard note"> | ||
<p><strong>Note:</strong> Chrome identifies allowed extensions with another key: <code>allowed_origins</code>, using the ID of the WebExtension. Refer to <a href="https://developer.chrome.com/apps/nativeMessaging#native-messaging-host">Chrome documentation for more details </a>and see <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_messaging#chrome_incompatibilities">Chrome incompatibilities below</a>.</p> | ||
<p><strong>Note:</strong> Chrome identifies allowed extensions with another key: <code>allowed_origins</code>, using the ID of the WebExtension. Refer to <a href="https://developer.chrome.com/apps/nativeMessaging#native-messaging-host">Chrome documentation for more details </a>and see <a href="#chrome_incompatibilities">Chrome incompatibilities below</a>.</p> | ||
</div> | ||
|
||
<h3 id="Windows_setup">Windows setup</h3> | ||
|
@@ -115,7 +115,7 @@ <h4 id="App_manifest_2">App manifest</h4> | |
"allowed_extensions": [ "[email protected]" ] | ||
}</pre> | ||
|
||
<p>(See note above about <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_messaging#chrome_incompatibilities">Chrome compatibility</a> regarding the <code>allowed_extensions</code> key and its counterpart in Chrome).</p> | ||
<p>(See note above about <a href="#chrome_incompatibilities">Chrome compatibility</a> regarding the <code>allowed_extensions</code> key and its counterpart in Chrome).</p> | ||
|
||
<p>The batch file then invokes the Python script:</p> | ||
|
||
|
@@ -465,4 +465,5 @@ <h2 id="Troubleshooting">Troubleshooting</h2> | |
|
||
<h2 id="Chrome_incompatibilities">Chrome incompatibilities</h2> | ||
|
||
<p>{{Page("Mozilla/Add-ons/WebExtensions/Chrome_incompatibilities", "Native_messaging")}}</p> | ||
<p>There are a number of differences between browsers that affect native messaging in web extensions, including the arguments passed to the native app, location of the manifest file, etc. | ||
These differences are discussed in <a href="/en-US/docs/Mozilla/Add-ons/WebExtensions/Chrome_incompatibilities#native_messaging">Chrome incompatibilities > Native messaging</a>.</p> |