[taler-docs] branch master updated: dd39: remove confusing example/suggestion

[gnunet]

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 905ffc59 dd39: remove confusing example/suggestion
905ffc59 is described below

commit 905ffc59c7d0b70cfab7cc829bd843df680d854a
Author: Florian Dold <florian@dold.me>
AuthorDate: Wed Jan 24 15:07:16 2024 +0100

    dd39: remove confusing example/suggestion
---
 design-documents/039-taler-browser-integration.rst | 12 +++++-------
 1 file 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
 ===========================

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.