Re: [w3c/browser-payment-api] Use first matching PaymentDetailsModifier (#541)

OK, that all makes sense. In that case I'd like us to explicitly reference [[serializedModifierData]] and talk about the process of sending each payment app (?) the serialized data, to tie things together.

I'm OK not doing it in show()/updateWith() for now, and keeping it here, as long as we have an issue marker and get it fixed as part of the CR transition.

-- 
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/pull/541#issuecomment-306482240

Received on Tuesday, 6 June 2017 13:15:52 UTC