Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173)

> even if it's slow, 

It's too fast right now. 

> and even if we have to make changes

I'd still be more in favour of incubation, not standardization. I'd like to see where Chrome's experiment/prototype with PayPal and other partners ends up. 

> Are there other people (e.g,. from Mozilla) who may not be actively implementing or testing PR API and who are interested in helping us with Payment Handler, or at least keeping an eye on it?

No. There is a team of us tracking this, but we are all actively working on PR API. We don't have the scope to contribute properly to the handlers work and ship PR in a reasonable time in an interoperable manner. 

Consider, we have literally no idea today if payment method modifiers even work interoperably. There are no tests and Chrome currently has them disabled. I've no idea if they are supported in Edge and if they will work interoperaby with Firefox. 

That should give everyone pause. Like serious pause: because modifiers change the total and can add displayItems. 

> We are actively seeking more testing resources for PR API. If it would be useful to you, I am happy to schedule a regular slot where, either by phone or chat or otherwise, we do testing project management to make sure we have targets and are reaching them.

Could definitely work: Need people to be proactively writing tests or reverse engineering implementation. 


-- 
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/issues/173#issuecomment-317734900