Cards added in payment method are not displaying without refreshing the payment request page |
||
Issue descriptionApp Version: 63.0.3224.0 Canary iOS Version: 9.3.5, 10.3.3, 11.0 Device: iPhone and iPad URL: https://madmath.github.io/samples/paymentrequest/credit-cards/ Steps to reproduce: 1. Launch chrome and redirect to above mentioned URL 2. Tap on the buy button and tap on the cards under payment 3. Tap on Add card button 4. Provide valid card details with billing address and tap on done button 5. Tap on cancel button 6. Tap on Buy button without refreshing the page. Observed results: The card added at step 4 is not displayed in payment method Note: After step 6, refresh the page and tap on buy button then the added card will display Note: Same behavior is noticed in desktop as well. Expected results: The added card should be displayed without refreshing the payment request page. Number of times you were able to reproduce: 5/5 Bug reproducible after clean install: Yes Bug reproducible after clearing cache and cookies: Yes Bug reproducible on Chrome Mobile on Android: Not tested Bug reproducible on Safari/Firefox: Firefox: NA, Safari: NA Bug reproducible on current stable build (App Version, iOS Version): No on M61 (Payment request API is a new feature from M62) Bug reproducible on the current beta channel build (App Version, iOS Version): Yes on M62 Beta Link to video/image: https://drive.google.com/a/google.com/file/d/0B8Cek8RsDbF8cXdvSHhlSGdjOXM/view?usp=sharing
,
Sep 26 2017
I'm fairly certain that's because the page in question creates the second PaymentRequest object immediately after PaymentRequest.show() is called. So the second object reads the credit cards before the user has added a new one. If the test code was creating the second PaymentRequest object after the first PaymentRequest.show() promise has been resolved (i.e., UI is closed), then you would see the new card in the second PaymentRequest window. Therefore, this behavior is an artifact of the test page and not the PaymentRequest implementation, unless we're willing to re-read credit cards inside of PaymentRequest.show() call instead of PaymentRequest constructor, which I do not recommend for performance reasons. I recommend closing this as WontFix.
,
Sep 27 2017
Completely agree with you rouslan@. Closing this as WontFix. |
||
►
Sign in to add a comment |
||
Comment 1 by rouslan@chromium.org
, Sep 26 2017Status: Assigned (was: Untriaged)