commit 078d8a11daec59f2df58b38c36f2616b51d2df77 parent 3cba35cb301c527edd4e6d8ccc39be9a400c3147 Author: Florian Dold <florian.dold@gmail.com> Date: Wed, 8 Apr 2020 22:31:48 +0530 elaborate on async API Diffstat:
| M | design-documents/001-new-browser-integration.rst | | | 10 | ++++++++++ |
1 file changed, 10 insertions(+), 0 deletions(-)
diff --git 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