- From: Rick Byers <notifications@github.com>
- Date: Mon, 11 May 2026 08:34:55 -0700
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 11 May 2026 15:35:02 UTC
RByers left a comment (w3c/payment-request#1066) FWIW I don't believe we should revert this. Without a viable replacement (no, capability delegation in it's current form is not it), Chrome will not unship our behavior here. So it would seem to be to be spec-fiction to have the spec indicate it's not allowed. Let's try to agree on a realistic plan to fully solve this use case (#1064) before suggesting we break the fix we have. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/payment-request/pull/1066#issuecomment-4422119334 You are receiving this because you are subscribed to this thread. Message ID: <w3c/payment-request/pull/1066/c4422119334@github.com>
Received on Monday, 11 May 2026 15:35:02 UTC