[Spec] Write the 'transaction UX' section #114
Conversation
The goal here is to enforce that User Agents do communicate the necessary information that will be signed over, but not to restrict their implementation of how to do so.
|
@domfarolino - I've straw-personed some minimal text here as a starting point. I'd love your thoughts on the best way to specify this without constraining UAs. |
| Payment Confirmation payment handler=] is selected. However, so that a | ||
| [=Relying Party=] can trust the information included in | ||
| {{CollectedClientPaymentData}}, the User Agent MUST ensure that the following | ||
| is communicated to the user: |
There was a problem hiding this comment.
This looks good! It is a tad COMEFROMey, so it might be nice to define an algorithm here that communicates the above-mentioned information in some UA way, and then invoking that algorithm from show(), but I think this is sufficient.
There was a problem hiding this comment.
I agree! Unfortunately Payment Request is implemented such that there is no actual concrete place where the payment handler 'takes over' :/
- Calls the Steps to check if a payment can be made in step 16.6.1
- Specifies a user interface to pick a handler in step 18
- Sets the internal
handlerslot in step 20 - ... and then stops specifying anything
So there's not really anything to hook onto here :(. If when we move away from Payment Request, I hope to make this more GOTO rather than COMEFROM :)
SHA: 0584229 Reason: push, by @stephenmcgruer Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
The goal here is to enforce that User Agents do communicate the necessary
information that will be signed over, but not to restrict their implementation
of how to do so.
Preview | Diff