- From: Stephen McGruer <notifications@github.com>
- Date: Wed, 12 Nov 2025 01:30:47 -0800
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 12 November 2025 09:30:51 UTC
stephenmcgruer left a comment (w3c/payment-request#1040) We discussed this issue at the Web Payments Working Group session ([minutes](https://www.w3.org/2025/11/11-wpwg-minutes.html#7816)) at TPAC 2025. Main points that I heard: - I voiced the opinion that I align generally with Marcos' opinion that feature detection here would be overkill - A TAG member (Martin) was asked about backwards compatibility wrt error codes; the reply was that it is reasonable for a specification to add new error codes and developers should generally be expected to handle that, but of course that web developers do not always do the expected thing. So as always, we should be diligent for breakage as implementors if/when a change rolls out. I took [an action item](https://www.w3.org/2025/11/11-wpwg-minutes.html#23f6) to sync up with Marcos to make sure we've thought it through, though generally I hope to resolve things just via this issue as I don't think it's particularly difficult. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/payment-request/issues/1040#issuecomment-3520962428 You are receiving this because you are subscribed to this thread. Message ID: <w3c/payment-request/issues/1040/3520962428@github.com>
Received on Wednesday, 12 November 2025 09:30:51 UTC