New issue
Advanced search Search tips

Issue 730641 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

[Payments] Web apps: registering does not take effect immediately

Project Member Reported by ma...@chromium.org, Jun 7 2017

Issue description

(1) Open two tabs, one on https://gogerald.github.io/pr/bobpaywebapp/ and one on https://rsolomakhin.github.io/pr/bob
(2) Register the payment app in one tab
(3) Switch tabs to pay with the newly registered payment app, and it's not available.

I'm not 100% sure of this bug. But it feels like sometimes a newly registered payment app is not available to pay right away. 


 
Not a bug, because https://rsolomakhin.github.io/pr/bob builds PaymentRequest object (and therefore queries payment apps) on page load.
Status: WontFix (was: Unconfirmed)

Comment 3 by ma...@chromium.org, Jun 7 2017

Status: Unconfirmed (was: WontFix)
Would still like someone to look into all cases if not that particular one. I've seen weirdness around registration. 
Status: Assigned (was: Unconfirmed)
Components: -UI>Browser>Autofill>Payments UI>Browser>Payments
Status: WontFix (was: Assigned)
This is because service worker registration is an asynchronous process which might take time, like web app manifest fetching, and my test web site (https://gogerald.github.io/pr/bobpaywebapp/) doesn't indicate when the registration is finished, so if you switch tab immediately, then the service worker registration might not finish yet.

The registration in bobpay.xyz shows a flag when registration is finished, the newly registered payment app is available after that.

Payment app providers should somehow show registration status for better user experience as bobpay.xyz.

So I think we could close this bug as WontFix 

Sign in to add a comment