- From: SECtim <notifications@github.com>
- Date: Wed, 04 Nov 2020 03:56:22 -0800
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 4 November 2020 11:56:35 UTC
Hi! While reading up on @crowgames's findings about the retry mechanism (#882, #904), I was a bit confused by the following statement: > A user cannot switch payment handlers during retry. **One can only change the things being retried** (eg. new credit card expiry date). _Originally posted by @marcoscaceres in https://github.com/w3c/payment-request/issues/882#issuecomment-549197510_ My understanding would be that _"the things being retried"_ refers to the `errorFields` argument of `retry()`. This led me to [the description](https://github.com/w3c/payment-request/blob/e71e17d5a646f708a22ba93b79349bc60374385e/index.html#L3088-L3224) of how a user agent must handle a `retry()` call. According to my understanding of that description, the user agent does not need to restrict modifications to the fields indicated by `errorFields`. Did I overlook the respective instructions in the spec? If not, I think it would make sense to clarify the specifications in that aspect. Cheers -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/payment-request/issues/933
Received on Wednesday, 4 November 2020 11:56:35 UTC