-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spec still talks about "payment app" #151
Comments
No, it's used intentionally. They are different things. A payment app is any app that handles payment requests forwarded to them by the UA. A payment handler is a new feature of the web platform that handles PaymentRequestEvents. Therefore a web app that employs a payment handler is a payment app. If you think that is not clear from the spec please can you suggest some edits? |
Argh... edit would be to remove any mention of "payment app". It already causes us a bunch of needless fights about two months ago because it's mega confusing. I'd prefer it not be mentioned anywhere. If we want to about "apps", then we can talk about web applications that serve as payment handlers, but that's it. |
I don't agree but let's give the spec some airtime and take feedback from people that are seeing it for the first time. I don't think this is a blocker for FPWD for that reason. Request that you close and we gather feedback post-FPWD on how these new concepts are received. |
I think the discussions that have happened have led us to being clearer in the spec. +1 to leaving it in the FPWD, and seeing if we get additional feedback. Ian |
@marcoscaceres wrote:
Agreed, we should minimize the amount of new terminology we require Web Developers to learn. |
Can we please remove payment app from the spec. We've updated other specs to talk about payment handlers.
Consider this a FPWD blocking issue.
The text was updated successfully, but these errors were encountered: