Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157)

This sounds good with minor corrections of a few details.

 - Dictionaries cannot have methods, so "canMakePayment" would be better as an event. This event would behave similar to the existing "paymentrequest" event.
 - When the "canMakePayment" event is disabled, I expect it to be not fired at all. Therefore, the event handler itself does not have a notion of being "disabled", because that information is external to the event handler. Nevertheless, the spec should mention disabling the event through settings and/or private browsing mode.
 - I agree that "canMakePayment" event handler should be optional. If the payment app does not have this event handler, then the browser should always show the payment app when its payment method is requested.

-- 
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/157#issuecomment-303842297