Closed ianbjacobs closed 6 years ago
Hi @marcoscaceres, I have made some edits to the text based on your comment.
Chrome supports payment method manifest, so I think it is appropriate to mention the concept of matching affected by information coming from the payment method owner. Whether we choose to name the Payment Method Manifest spec (a FPWD) is a separate question. (I think we should, FWIW.)
Chrome supports payment method manifest, so I think it is appropriate to mention the concept of matching affected by information coming from the payment method owner.
You know I love Chrome, but I think it's unfair to mention it, because we don't know if any other browser vendors is going to support it. Mozilla currently has no plans to support it, and I don't think anyone else has said anything about supporting it (though it may not be possible to support payment handlers without it... but I've no idea, I've not looked that much into it).
@marcoscaceres wrote
"Mozilla currently has no plans to support it, and I don't think anyone else has said anything about supporting it (though it may not be possible to support payment handlers without it... but I've no idea, I've not looked that much into it)."
I think you and I should discuss it the manifest spec since I think it's an important complement to Payment Handler API.
I think you and I should discuss it the manifest spec since I think it's an important complement to Payment Handler API.
Always happy to chat, but we are not quite ready to discuss supporting more stuff until we have a solid implementation of Payment Request and Basic Card. Too much work, too little time :(
@marcoscaceres,
I hear the prioritization and understand the resource crunch.
Nonetheless, I think it is ok to mention this in an informative note at this time (where we have FPWDs, like Payment Handler and Payment Method Manifest)
Ian
Preview | Diff