- From: Stephen McGruer <notifications@github.com>
- Date: Wed, 20 May 2026 05:48:19 -0700
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 20 May 2026 12:48:23 UTC
stephenmcgruer left a comment (w3c/payment-request#1066) I'd like to keep conversation to the issue as Rick has left a more indepth comment there (https://github.com/w3c/payment-request/issues/1064#issuecomment-4421890389), but just to note: > As it stands, this documents single-engine behavior as a literal standard. To the best of my knowledge, this is incorrect. The current text is in the Candidate Recommendation Draft, which [is explicitly not a standard](https://www.w3.org/standards/types/#x4-2-1-candidate-recommendation-draft): > These documents MUST NOT be cited as W3C standards and may or may not become W3C standards. The standard document for Payment Request continues to be https://www.w3.org/TR/2022/REC-payment-request-20220908/ (correct me if I'm wrong @ianbjacobs !). Again, let's continue discussion on the issue, just felt it was important to address this specific statement in context. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/payment-request/pull/1066#issuecomment-4498537979 You are receiving this because you are subscribed to this thread. Message ID: <w3c/payment-request/pull/1066/c4498537979@github.com>
Received on Wednesday, 20 May 2026 12:48:23 UTC