Re: [w3c/payment-request] Changes resulting from 28 February PING privacy review (#843) from pes on 2019-03-06 (public-webpayments-specs@w3.org from March 2019)

From: pes <notifications@github.com>
Date: Wed, 06 Mar 2019 12:33:58 -0800
To: w3c/payment-request <payment-request@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/payment-request/pull/843/c470265584@github.com>

@rsolomakhin @ianbjacobs 

Just so that my understanding is clear, can someone describe what `canMakePayment` should return in each of the following scenarios:

1. I'm using Firefox, I haven't ever used any Credit Card info in FF (i.e. it doesn't know if I have a visa).  Website calls `canMakePayment` with credit-card and visa.
2. Same as above, but I've disabled Payment Request API (`dom.payments.request.enabled = false`)
3. I'm using Firefox, but `supportedMethods = "apple-pay".

@marcoscaceres just trying to understand what you mean by "FF lies…".  Can you describe what you meant there?

-- 
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-request/pull/843#issuecomment-470265584

Received on Wednesday, 6 March 2019 20:34:19 UTC