Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes resulting from 28 February PING privacy review #843

Merged
merged 18 commits into from Mar 12, 2019
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion index.html
Expand Up @@ -5295,7 +5295,7 @@ <h2 id="canmakepayment-protections">
<p data-link-for="PaymentRequest">
The <a>canMakePayment()</a> method enables the payee to determine
— before calling <a>show()</a> — whether the user agent knows of any <a>payment handlers</a> available to the user that support the <a>payment methods</a> provided to the <a>PaymentRequest<a> <a data-lt="PaymentRequest.PaymentRequest()">constructor</a>.
advantage of the API. This enables the payee to fall back to a legacy
If no <a>payment handlers</a> support the <a>payment methods</a>, this enables the payee to fall back to a legacy
checkout experience. Because this method shares some information with
ianbjacobs marked this conversation as resolved.
Show resolved Hide resolved
the payee, user agents are expected to protect the user from abuse of
the method. For example, user agents may reduce user fingerprinting
ianbjacobs marked this conversation as resolved.
Show resolved Hide resolved
Expand Down