@@ -16,13 +16,7 @@ do not modify/remove the key in ``manifest.json``.
1616
1717## Communicating with the extension
1818
19- The simplest way for web pages to talk to the extension is to load the script
20- `` chrome-extension://pfboblefjcgdjicmnffhdgionmgcdmne/u2f-api.js `` . This installs
21- a namespace `` u2f `` as described in U2F JavaScript API draft sent to the mailing
22- list. If you are willing to load this script in your pages, you can safely skip
23- the remainder of this section.
24-
25- The U2F JavaScript API draft also describes how websites can talk directly to
19+ The U2F JavaScript API draft describes how websites can talk directly to
2620the extension via a [ MessagePort] [ messageport ] , in cases where they do not
2721whish to load a script from the extension. How a port to this extension is
2822obtained depends on whether the source origin is whitelisted as * externally
@@ -71,8 +65,6 @@ function getIframePort(callback) {
7165};
7266```
7367
74- For a full example refer to `` u2f-api.js `` .
75-
7668The drawback of this transport is that the websites [ TLS channel id] [ channelid ]
7769will not be available to the extension, and thus not included in signed U2F
7870assertions.
@@ -92,9 +84,7 @@ obtaining a message port to the extension is simpler:
9284```
9385
9486The returned port will be a Chrome runtime port object, which has slightly
95- different syntax for how event handlers are added. Again, see `` u2f-api.js ``
96- for a full example and how to wrap this in a HTML5 MessagePort compatible
97- interface.
87+ different syntax for how event handlers are added.
9888
9989### Extending the extension with an external helper
10090
0 commit comments