Re: [w3c/browser-payment-api] Security hole in payment API when a constructor from a no longer active document is invoked (#361)

@rsolomakhin No, I cannot.  I have way too many other things on my plate to start editing this spec.  Even just taking the time to look for issues in it was a significant problem time-wise.  I expect the editors to actually do their job and address issues that are raised, instead of asking the issue filers to also take on fixing them.

-- 
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/browser-payment-api/issues/361#issuecomment-265511542