[[waitForUpdate]] must be set to true always after dispatch.

[marcoscaceres]

Elsewhere, @danyao wrote:

From my reading of the spec, [[waitForUpdate]] is only set to true after updateWith() is called. Am I missing something?

Yes, indeed a small spec bug. Will send a patch.

[danyao]

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?

[marcoscaceres]

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 ***@***.***> 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.