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

So I think this addresses the problem, but not in the ideal way. It should be part of the show() algorithm, IMO.

Also, currently we only store the modifiers as serialized strings in the [[serializedModifierData]] slot. It's a bug in the current spec that nobody every references that slot. We should probably reference it! But now I'm confused as to why it needs to be JSON-serialized at all. Will it be sent across processes? Is each payment app going to process it differently? If so we should make that explicit, like we kind of do for [[serializedModifierData]].

-- 
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-305925521