- From: Marcos Cáceres <notifications@github.com>
- Date: Sat, 30 Mar 2019 22:30:19 -0700
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 31 March 2019 05:30:41 UTC
Yeah, well spotted. I'll draft a PR for the spec. We'll need to check if we have a test for that - but it should be easy to test. > On Mar 29, 2019, at 2:56 AM, Danyao Wang <notifications@github.com> wrote: > > Hi @marcoscaceres! I noticed that the payer detail change algorithm also fires a PaymentRequestUpdateEvent. But in this case, the algorithm doesn't set [[waitForUpdate]] to true immediately after event dispatching. Should we make it align with the other cases? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or mute the thread. > -- 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/payment-request/issues/854#issuecomment-478313505
Received on Sunday, 31 March 2019 05:30:41 UTC