diff options
author | Christian Grothoff <christian@grothoff.org> | 2020-04-29 22:28:29 +0200 |
---|---|---|
committer | Christian Grothoff <christian@grothoff.org> | 2020-04-29 22:28:29 +0200 |
commit | 273bbdf924c7d011c6249334e94a34a04a18fe39 (patch) | |
tree | ed36a0f50d9842420b1899b3ff95fa5e0bf8c9de /design-documents/001-new-browser-integration.rst | |
parent | 220b06cf14f44f3241590e8e1cc08d23d44885e0 (diff) | |
parent | d6df3784a31df42b5d2e77ef92259b62c7a6c47b (diff) | |
download | docs-273bbdf924c7d011c6249334e94a34a04a18fe39.tar.gz docs-273bbdf924c7d011c6249334e94a34a04a18fe39.tar.bz2 docs-273bbdf924c7d011c6249334e94a34a04a18fe39.zip |
Merge branch 'master' of git+ssh://git.taler.net/docs
Diffstat (limited to 'design-documents/001-new-browser-integration.rst')
-rw-r--r-- | design-documents/001-new-browser-integration.rst | 26 |
1 files changed, 23 insertions, 3 deletions
diff --git a/design-documents/001-new-browser-integration.rst b/design-documents/001-new-browser-integration.rst index f436a4f7..8dbe2a43 100644 --- a/design-documents/001-new-browser-integration.rst +++ b/design-documents/001-new-browser-integration.rst @@ -1,10 +1,30 @@ Design Doc 001: New Browser Integration ####################################### -.. note:: +.. warning:: - This design document is currently a draft, it - does not reflect any implementation decisions yet. + We have decided not to follow through with the proposed solution in this + design doc. We care a lot about a nice upgrade path for when better + browser integration becomes available. Encouraging the ``#taler://`` fragment + based integration might lead merchant frontends to **only** support this type + of integration. + + Instead, the following path will be taken: + + 1. CSS-based presence detection will be removed from the wallet, + as there is no satisfactory upgrade path to better mechanisms + 2. Manual triggering will be implemented as described in this design doc. + 3. The ``webRequest`` permission that allows ``"Taler: "`` header based + browser integration will become opt-in. + 4. The interactive API will be put on hold. Instead, SPAs should + ask the user to open the wallet popup (and/or render a QR code for mobile wallets). + 5. To enable easier integration for merchants, the reference merchant backend + might include a page to trigger payments, which displays the QR code + correctly, does long-polling via JS and serves the ``"Taler: "`` header. + 6. The presence detection ``taler://`` URI described in this document + will **not** be supported, as allowing presence detection might + encourage merchants to treat mobile / detached wallets as 2nd class + citizens. Summary ======= |