search

w3c / payment-request

Payment Request API
https://www.w3.org/TR/payment-request/
Other
489 stars 135 forks source link

Change what canMakePayment() means #806

Closed marcoscaceres closed 5 years ago

marcoscaceres commented 5 years ago

During the F2F, we came to a consensus that "canMakePayment" means "the user agent supports the PMIs" - but it does not mean that there is a payment instrument set up. We concluded that we might add something to check if there is an active instrument in the future.

closes #800

The following tasks have been completed:

Implementation commitment:

Optional, Impact on Payment Handler spec?

@ianbjacobs and @rsolomakhin, probably some impact! ☄️

marcoscaceres commented 5 years ago

Redid the test and updated MDN.

rsolomakhin commented 5 years ago

How far in the future are we thinking about the active instrument check?

marcoscaceres commented 5 years ago

I’m unsure - that was really unclear to me. Do we want it now? Can we live without it for V1?

rsolomakhin commented 5 years ago

I would prefer to implement it soon, but don't want to force the other implementers or block the CR process.

marcoscaceres commented 5 years ago

I guess we could at least draft it up and put everything in place, then check implementation plans.

rsolomakhin commented 5 years ago

Good idea :+1:

marcoscaceres commented 5 years ago

We couldn’t implement in Firefox for at least 3 month. We have a big backlog to finish just with the current stuff. That means 6 months till we would have something in release.

marcoscaceres commented 5 years ago

Unrelated but, Mozilla folks put together this great wiki page that shows our implementation priorities, with explanations, and stuff we still need to do (@ianbjacobs and Chairs, you might like it):

https://wiki.mozilla.org/Firefox/Features/Web_Payments/DOM

It gives a good sense of where we are at and updates dynamically as we fix things, so good to periodically check.