Re: [w3c/payment-request] Add support for merchant validation (#751)

@aestes, wrote: 
> This looks good, although I was surprised to see that MerchantValidationEvent.validationURL can be initialized from the eventInitDict. Is that there for payment handlers' sake?

It's not handler related - but could be used there too, I guess: It used to be a requirement in the DOM Spec that there be a 1:1 relationship between initialization dictionary members and Event interface attributes.
 
@domenic, I see this has now changed in the [inner event creation steps](https://dom.spec.whatwg.org/#inner-event-creation-steps). It seems that requirement was loosened up a bit:

> For each member → value in dictionary, if event has an attribute whose identifier is member, then initialize that attribute to value.

Or does the 1:1 relationship rule still hold?

@aestes, the `.complete()` still rely on `.isTrusted` - so IMO it would still be good to define how URLs are resolved when the MerchantValidationEvent is constructed (even if constructed unsafely in JS). 

-- 
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/pull/751#issuecomment-414854692