Re: [w3c/payment-handler] Missing question mark, (#163)

@rsolomakhin 
As far as I know, your understanding is correct. 👍
So, I have a plan to remove the related sentence first from the spec.
For example, the spec says that event.[[windowClient]] can be null here. [1]
> 6. If event.[[windowClient]] is not null, then:
>> 1. If event.[[windowClient]].visibilityState is not "unloaded", reject promise with a DOMException whose name is "InvalidStateError" and abort these steps.

On the other hands, it seems to be a only case that resolves with null when newContext's origin and SW's origin are different according to the SW's spec[2].
So, my plan is that I'll re-check them again and then make a pull request.
(My co-worker @jungkees can help me as SW's spec writer.)

[1] https://w3c.github.io/payment-handler/#dfn-windowclient
[2] https://w3c.github.io/ServiceWorker/#clients-openwindow (openWindow section 6-9)

-- 
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-handler/issues/163#issuecomment-305241262