Open
Bug 1496656
Opened 6 years ago
Updated 1 year ago
user activation should survive await microtask
Categories
(Core :: DOM: Web Payments, defect, P2)
Core
DOM: Web Payments
Tracking
()
NEW
People
(Reporter: marcosc, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [webpayments-reserve])
Attachments
(1 file)
693 bytes,
text/html
|
Details |
User activation is not surviving a single await in the same function. ``` // Triggered by a click async function usingAwait() { const request = new PaymentRequest(methods, details); // This works... const result = await request.canMakePayment(); // Tick! this now fails const response = await request.show(); } ``` STR: 1. load attached file 2. click on `usingAwait` button. 3. Check error console. Expected: .show() should show the payment sheet. Actual: Shows "User activation is now required to call PaymentRequest.show()" "SecurityError: The operation is insecure." See also the "usingPromises", where it works as expected!
Reporter | ||
Updated•6 years ago
|
Blocks: paymentrequest
Reporter | ||
Updated•6 years ago
|
Priority: -- → P3
Updated•6 years ago
|
Flags: qe-verify?
Priority: P3 → P2
Whiteboard: [webpayments-reserve]
Comment 1•6 years ago
|
||
Moving this back to P3 as I don't think it's actionable yet.
Priority: P2 → P3
Updated•6 years ago
|
Priority: P3 → P2
Updated•5 years ago
|
Summary: "Triggered by user active" should survive await micotask → "Triggered by user active" should survive await microtask
Reporter | ||
Updated•4 years ago
|
Summary: "Triggered by user active" should survive await microtask → user activation should survive await microtask
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•