Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138)

adrianhopebailie commented on this pull request.



> @@ -362,13 +361,12 @@
         "PaymentManager.instruments">instruments</a> and <a data-lt=
         "PaymentManager.wallets">wallets</a>.
         </li>
-        <li>Payment apps make use of <a>service worker</a>s, starting with
-        registration of their capabilities with the user agent. A service
-        worker registration has zero or one <a>payment handler</a>. However, an
-        origin may implement a payment app with more than one service worker
-        registration.
+        <li>Payment apps make use of <a>service worker</a>s which must define a
+        <a>payment handler</a> to handle the <a>PaymentRequestEvent</a>s that
+        are raised by the user agent.

> t is not clear to me that user agents "raise" these events. Rather, they result from the PR API invocation.

They do. There are two things happening here.

  1. The user agent handles the PR API invocation
  2. The user agent raises a `PaymentRequestEvent`

Technically these can both happen without the other and in future that may be the case. The browser may have other APIs or processes that trigger a `PaymentRequestEvent` in future

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments-payment-handler/pull/138#discussion_r111897712