Re: [w3c/payment-request] Adding support for private-label credit cards (#662)

> How about we let PaymentRequestUpdateEvent sprout methodName and details attributes - we can null the details by default, and adding the method name should be trivial.

I wonder if `details` would be confusingly generic if it's not used for other events. Perhaps `methodDetails` would make it's purpose more clear?

If you're intentionally leaving the name generic so it can be used from other change events in the future then the spec's description of `details` should make it clear that the details are about a payment method only when the event is a `paymentmethodchanged` and it's null otherwise.

-- 
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/662#issuecomment-360379491