Closed Bug 1496656 Opened 7 years ago Closed 2 months ago

user activation should survive await microtask

Categories

(Core :: DOM: Web Payments, defect, P3)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1971459

People

(Reporter: marcosc, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [webpayments-reserve], dom-lws-bugdash-triage)

Attachments

(1 file)

Attached file reduced.html
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!
Priority: -- → P3
Flags: qe-verify?
Priority: P3 → P2
Whiteboard: [webpayments-reserve]
Moving this back to P3 as I don't think it's actionable yet.
Priority: P2 → P3
Priority: P3 → P2
See Also: → 1447178
Summary: "Triggered by user active" should survive await micotask → "Triggered by user active" should survive await microtask
Summary: "Triggered by user active" should survive await microtask → user activation should survive await microtask
Severity: normal → S3

Changing qe-verify? to qe-verify+.

Flags: qe-verify? → qe-verify+
Severity: S3 → S4
Priority: P2 → P3
Whiteboard: [webpayments-reserve] → [webpayments-reserve], dom-lws-bugdash-triage
Status: NEW → RESOLVED
Closed: 2 months ago
Duplicate of bug: 1971459
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: