Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173)

@adrianhopebailie wrote: "In terms of the API would a design where I don't repeat the same instrument twice be better? "

I intentionally offered that design with the expectation that some information about the instrument might change if used in a default context. If that is never useful, we should consider other options.

Your proposal (a defaultInstrumentKey) does not on its own give you the necessary second key to be able to distinguish "default" from "all." This could be done in various ways. For example, if displayed and selected in a default context, the browser could send the payment an additional piece of data like "defaultSelected" to complement the instrumentKey of the selected instrument.

Summary:
 * It feels like we need two pieces of data.
 * That might take various forms such as "a second key" or "a flag when the default has been displayed and selected"
 * I am not at all wedded to my proposal that involved some duplication. There may also be ways to combine ideas like:

   defaultInstrumentKey ::= instrumentKey
   defaultInstrumentName ::= NameWhenDisplayedAsDefault

It would be good to hear what people think is necessary for a good user experience. Does the payment handler need to specify a special label for the default case, or could the browser do that in a manner consistent across payment apps?

Ian

-- 
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-handler/issues/173#issuecomment-308218745