Re: [w3c/browser-payment-api] Should show() be renamed? (#127)

>  in some cases a payment app may be able to fully automate its response without user interaction, in which case nothing would actually be shown

Even if that is a possibility, from that it does not follow that the method ought to be renamed. In those cases, I would think the `show()` call would simply just be a no-op, and nothing would be presented to the user. Which is fine.

As far what the resulting user experience is for an end user in a screen reader or other AT, of course their SR/AT is going to present the dialog to them in a non-visual way, and so “show” is simply shorthand for “present something to the user”—in a similar way to the convention that say, telling a user to “press the *Foo* button” in a software UI doesn’t mean a physical button has somehow been created for them to work with, and that they have to actually “press” it in the same way they do a physical button (that is, by actually physically pushing the button down  their finger so that it physically moves down)…

---
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/issues/127#issuecomment-207656273