diff options
author | Florian Dold <florian@dold.me> | 2024-01-24 15:07:16 +0100 |
---|---|---|
committer | Florian Dold <florian@dold.me> | 2024-01-24 15:07:16 +0100 |
commit | 905ffc59c7d0b70cfab7cc829bd843df680d854a (patch) | |
tree | d0cac91d91a983eac33d919bff2a21e357960eb0 /design-documents | |
parent | 4c60ed435413607769fe48115a7ab44335efb78b (diff) | |
download | docs-905ffc59c7d0b70cfab7cc829bd843df680d854a.tar.gz docs-905ffc59c7d0b70cfab7cc829bd843df680d854a.tar.bz2 docs-905ffc59c7d0b70cfab7cc829bd843df680d854a.zip |
dd39: remove confusing example/suggestion
Diffstat (limited to 'design-documents')
-rw-r--r-- | design-documents/039-taler-browser-integration.rst | 12 |
1 files changed, 5 insertions, 7 deletions
diff --git a/design-documents/039-taler-browser-integration.rst b/design-documents/039-taler-browser-integration.rst index 029ca6d4..e34a8d00 100644 --- a/design-documents/039-taler-browser-integration.rst +++ b/design-documents/039-taler-browser-integration.rst @@ -54,13 +54,7 @@ The problems with individual browsers are: either. Another issue is that Websites can't easily find out whether a browser -extension handling the ``taler://`` protocol is installed. To avoid using this -information for fingerprinting, anchors could provide an alternative ``href`` -in case the main one is not handled, such as: - -.. code:: html - - <a href="taler://pay/..." handler-unavailable-href="https://wallet.taler.net/">...</a> +extension handling the ``taler://`` protocol is installed. Requirements ============ @@ -184,6 +178,10 @@ Other Alternatives the Web Payments API would not support the withdrawal flow (``taler://withdraw`` URIs). +* Browsers could provide anchor elements with a fallback when the protocol isn't supported, such as + ``<a href="taler://pay/..." handler-unavailable-href="https://wallet.taler.net/">...</a>``. + + Related Work and References =========================== |