taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 4362ba6cc4044b22ff53f1a63611b6c42b55209f
parent 905ffc59c7d0b70cfab7cc829bd843df680d854a
Author: Sebastian <sebasjm@gmail.com>
Date:   Wed, 24 Jan 2024 11:20:55 -0300

comment on window.taler injection

Diffstat:
Mdesign-documents/039-taler-browser-integration.rst | 6+++++-
1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/design-documents/039-taler-browser-integration.rst b/design-documents/039-taler-browser-integration.rst @@ -121,6 +121,7 @@ The following features are supported: * ``uri`` will hijack anchor elements (``<a href="taler://..." onclick=...>``) and replace their onclick handler with a different handler that lets the webexension wallet handle the ``taler://`` URI. + * (future): ``api`` will inject the ``window.taler`` API into the page @@ -142,11 +143,14 @@ the URI in the browser's address bar. * A neat feature of the anchor hijacking is that the ``taler://`` URI can be always be copied in the browser (via "copy link address"). Clicking the link always results in either: + * The native URI handler, if no Taler Wallet webextension is installed and no onclick handler is defined * The execution of the websites onclick handler if no Taler Wallet webextension is installed * Triggering the webextension wallet to handle the ``taler://`` URI. - +* Future ``window.taler`` injection should be based on user preferences on + sites where the user has explicitly accepted to disclose that is owner of a + Taler wallet. Other Alternatives ==================