Re: [w3c/payment-handler] Add userHint to PaymentManager (#206)

> Regardless, the spec should not concern itself with UI details, correct?

It shouldn't -- but I don't consider this a detail. I think it's a confusing semantic. We don't have to get into *how* it will be shown, but developers should know the semantics behind the thing. And right now, I think those are too ill-defined.

You've already got essentially a bunch of hints (+constraints) -- which we've called "Payment Instruments" ... and now we're adding another top-level "hint". If we're not clear to developers what should be put there and when it will be shown -- it's kind of a big deal. If developers we're the same information in two different places and then not saying what should trigger when it will be used, there's confusion -- and that will translate into user confusion and people thinking it's the payment handler's fault.

One way to remedy this is to say that the user agent should *either* use payment instruments as hints OR use `userHint`. That sends a clear message to the developer on what makes sense to put in `userHint`. Other similar choices could be made, but *some* kind of constraint should be put here if we're adding this thing, IMO.

-- 
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/pull/206#issuecomment-325004033