-
Notifications
You must be signed in to change notification settings - Fork 20
add requestSecurityCode member to BasicCardRequest #78
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm ok with this
Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1546859 |
Sent a patch to Gecko. Note that it only patches the DOM implementation. We don't have a basic card UI. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks right 👍
We should probably add a manual test before merging. |
Good idea.
…--Rouslan
On Mon, Apr 29, 2019 at 5:08 PM Marcos Cáceres ***@***.***> wrote:
We should probably add a manual test before merging.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#78 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAH3EGOCXRXOGJKFXDR6RATPS5PWVANCNFSM4HIHYUZA>
.
|
@rsolomakhin or @danyao, just wondering if this ever landed in Chrome? |
This did not land in Chrome yet, @marcoscaceres . |
@rsolomakhin thanks for confirming. I guess we should wait till it's in Chrome before we land this, otherwise it might confuse people. |
I like this and believe this makes sense |
@rsolomakhin or @danyao, any update on the Chrome side about supporting this? |
Hi @marcoscaceres , at this point we're investing heavily into payment handlers (both web based and OS-specific apps), so let's bypass waiting for Chrome to update it's basic-card implementation. Instead, let's update the spec and encourage payment apps that implement the basic-card standard to implement support for this new field as well. WDYT? |
Ah, just stumbled onto https://blog.chromium.org/2020/01/rethinking-payment-request-for-ios.html Sounds like we might want to wrap up Basic Card entirely then. |
The Basic Card standard can exist for 3rd party payment handlers to implement and for merchants to use, if they wish. It's just not Google's cup of tea to implement it, though. We'd much rather focus on Payment Request and Payment Handler standards. Edit: More precise wording. |
I think that we should maintain Basic Card as a Note. |
Ok, the above sounds like a plan. |
Relates to
w3c/payment-request#97
It does not close that issue because this solution is payment method specific (and also does not address all the fields within Basic Card; however it does address the one that has been cited).
The following tasks have been completed:
Implementation commitments:
Preview | Diff