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

From: aestes <notifications@github.com>
Date: Thu, 14 Mar 2019 16:53:45 -0700
To: w3c/payment-request <payment-request@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/payment-request/pull/843/c473108537@github.com>

> This is how Safari works:
> 
> ![screenshot 2019-03-05 16 12 37](https://user-images.githubusercontent.com/870154/53782475-80fdb900-3f61-11e9-968c-3d5cb8136911.png)

I should clarify something here. This option influences the return value of the [canMakePaymentsWithActiveCard API](https://developer.apple.com/reference/applepayjs/applepaysession/1778000-canmakepaymentswithactivecard) in Apple Pay JS (and soon the hasEnrolledInstrument API in Payment Request).

When that option is unchecked (or the window is in Private Browsing), canMakePaymentsWithActiveCard will behave as if canMakePayments were called instead, returning true whenever Apple Pay is supported even if there are no enrolled instruments.

Neither this checkbox nor Private Browsing influence the result of canMakePayments in Apple Pay JS or canMakePayment in Payment Request.

-- 
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-473108537

Received on Thursday, 14 March 2019 23:54:07 UTC