From 4bb8e8319aa0aadd1b1ac9ac8a3f234982c8f172 Mon Sep 17 00:00:00 2001
From: Ade Bateman
+ If the user agent rejects the call to show() to
+ protect the user, then return a promise rejected with a
+ "SecurityError" DOMException. For example, this
+ might occur if the user agent requires a user gesture to
+ allow a page to call show(), or the user agent may
+ limit the rate at which a page can call show(), as
+ described in the the privacy
+ considerations section.
+
+ Implementations are expected to experiment in this area.
+ Developers using the payment request API should investigate and
+ anticipate such experiments and understand under what
+ circumstances a SecurityError might occur.
+
This allows user agents to apply heuristics to detect and prevent
abuse of the canMakePayment() method for fingerprinting
@@ -2677,7 +2694,7 @@
DOMException.
- If the user agent rejects the call to show() to - protect the user, then return a promise rejected with a - "SecurityError" DOMException. For example, this - might occur if the user agent requires a user gesture to - allow a page to call show(), or the user agent may - limit the rate at which a page can call show(), as - described in the the privacy - considerations section. + Optionally, if the user agent wishes to disallow the call + to show() to protect the user, then return a promise + rejected with a "SecurityError" DOMException. For + example, the user agent may require the call to be + triggered by user activation, or may limit the rate at + which a page can call show(), as described in the the + privacy considerations section.
-+
Implementations are expected to experiment in this area. Developers using the payment request API should investigate and anticipate such experiments and understand under what - circumstances a SecurityError might occur. + circumstances a "SecurityError" DOMException might + occur.