[taler-docs] branch master updated: elaborate on async API

[gnunet]

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 078d8a1  elaborate on async API
078d8a1 is described below

commit 078d8a11daec59f2df58b38c36f2616b51d2df77
Author: Florian Dold <address@hidden>
AuthorDate: Wed Apr 8 22:31:48 2020 +0530

    elaborate on async API
---
 design-documents/001-new-browser-integration.rst | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/design-documents/001-new-browser-integration.rst 
b/design-documents/001-new-browser-integration.rst
index 1601f71..c53ae85 100644
--- a/design-documents/001-new-browser-integration.rst
+++ b/design-documents/001-new-browser-integration.rst
@@ -165,6 +165,9 @@ of the ``taler://check-presence`` fragment to allow a 
placeholder for the extens
   can open a new tab/window and communicate the updated extension ID back to
   original SPA page.
 
+Once the Website has obtained the extension ID, it can use the 
``runtime.connect()`` function
+to establish a communication channel to the extension.
+
 
 Alternatives
 ============
@@ -177,3 +180,10 @@ Alternatives
 * convince Google and/or Mozilla to implement a general mechanism
   where extensions can offer a "service" that websites can then
   connect to without knowing some particular extension ID.
+
+Drawbacks
+=========
+
+* Firefox currently does not support messages from a website to an extension, 
and currently
+  cannot support the asynchronous wallet API.
+  There is a bug open for this issue: 
https://bugzilla.mozilla.org/show_bug.cgi?id=1319168

-- 
To stop receiving notification emails like this one, please contact
address@hidden.