path: root/design-documents/001-new-browser-integration.rst
diff options
authorFlorian Dold <>2020-04-08 22:31:48 +0530
committerFlorian Dold <>2020-04-08 22:31:48 +0530
commit078d8a11daec59f2df58b38c36f2616b51d2df77 (patch)
tree68da8b66d8789034b32493a40b2b10281e60bf44 /design-documents/001-new-browser-integration.rst
parent3cba35cb301c527edd4e6d8ccc39be9a400c3147 (diff)
elaborate on async API
Diffstat (limited to 'design-documents/001-new-browser-integration.rst')
1 files changed, 10 insertions, 0 deletions
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.
@@ -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.
+* 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: