[w3c/payment-request] maxprofs (#803)
- Re: [w3c/payment-request] maxprofs (#803)
- Re: [w3c/payment-request] maxprofs (#803)
- Re: [w3c/payment-request] maxprofs (#803)
- Re: [w3c/payment-request] maxprofs (#803)
Re: [w3c/payment-request] Follow up on APA Comments on Web Payments FPWDs (#735)
[w3c/payment-request] Added section and paragraph on accessibility considerations (#802)
- Re: [w3c/payment-request] Added section and paragraph on accessibility considerations (#802)
- Re: [w3c/payment-request] Added section and paragraph on accessibility considerations (#802)
[w3c/payment-request] Way of detecting if can make payment (#801)
[w3c/payment-request] Meaning of canMakePayment() (#800)
[w3c/payment-request] Consider specifying a testing IDL for a mock payment UI (#799)
- Re: [w3c/payment-request] Consider specifying a testing IDL for a mock payment UI (#799)
- Re: [w3c/payment-request] Consider specifying a testing IDL for a mock payment UI (#799)
[w3c/payment-request] Make Basic Card Payment Method Spec an informative reference (#798)
- Re: [w3c/payment-request] Make Basic Card Payment Method Spec an informative reference (#798)
- Re: [w3c/payment-request] Make Basic Card Payment Method Spec an informative reference (#798)
- Re: [w3c/payment-request] Make Basic Card Payment Method Spec an informative reference (#798)
- Re: [w3c/payment-request] Make Basic Card Payment Method Spec an informative reference (#798)
[w3c/webpayments-methods-tokenization] Should tpans be captured? (#53)
[w3c/payment-request] Treat scroll as a user gesture for PaymentRequest.show() (#797)
[w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796)
Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608)
Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765)
- Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765)
- Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765)
- Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765)
- Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765)
Re: [w3c/payment-request] Sensible defaults for dictionary members (#780)
[w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795)
- Re: [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795)
- Re: [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795)
- Re: [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795)
- Re: [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795)
Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680)
- Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680)
- Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680)
- Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680)
- Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680)
[w3c/payment-request] Remove PaymentItem.type (#794)
- Re: [w3c/payment-request] Remove PaymentItem.type (#794)
- Re: [w3c/payment-request] Remove PaymentItem.type (#794)
- Re: [w3c/payment-request] Remove PaymentItem.type (#794)
- Re: [w3c/payment-request] Remove PaymentItem.type (#794)
- Re: [w3c/payment-request] Remove PaymentItem.type (#794)
Re: [w3c/payment-handler] Simplifying functional event handling (#305)
- Re: [w3c/payment-handler] Simplifying functional event handling (#305)
- Re: [w3c/payment-handler] Simplifying functional event handling (#305)
[w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327)
- Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327)
- Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327)
- Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327)
- Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327)
- Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327)
- Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327)
- Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327)
- Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327)
Re: [w3c/webpayments-methods-tokenization] Better orient the reader (#51)
[w3c/payment-request] Should we validate nonsense payer error properties? (#793)
- Re: [w3c/payment-request] Should we validate nonsense payer error properties? (#793)
- Re: [w3c/payment-request] Should we validate nonsense payer error properties? (#793)
- Re: [w3c/payment-request] Should we validate nonsense payer error properties? (#793)
- Re: [w3c/payment-request] Should we validate nonsense payer error properties? (#793)
[w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
- Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
- Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
- Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
- Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
- Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
- Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
- Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
- Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
- Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
- Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
- Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
- Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
- Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
- Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
- Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
- Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)
Re: [w3c/payment-method-basic-card] Drop supportedTypes? (#59)
Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224)
- Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224)
- Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224)
- Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224)
[w3c/payment-request] test suite that checks whether shipping options can be updated (#791)
- Re: [w3c/payment-request] test suite that checks whether shipping options can be updated (#791)
- Re: [w3c/payment-request] test suite that checks whether shipping options can be updated (#791)
- Re: [w3c/payment-request] test suite that checks whether shipping options can be updated (#791)
Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223)
- Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223)
- Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223)
- Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223)
Re: [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248)
- Re: [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248)
- Re: [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248)
Re: [w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249)
- Re: [w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249)
- Re: [w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249)
Re: [w3c/payment-request] Support requesting billing address (#749)
Re: [w3c/payment-request] Rename `PayerErrorFields` to be like `AddressErrors` and `BasicCardErrors` (#782)
[w3c/payment-method-basic-card] Editorial: Fixed grammatical error and link to PaymentRequest interface (#61)
- Re: [w3c/payment-method-basic-card] Editorial: Fixed grammatical error and link to PaymentRequest interface (#61)
- Re: [w3c/payment-method-basic-card] Editorial: Fixed grammatical error and link to PaymentRequest interface (#61)
Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777)
- Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777)
- Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777)
- Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777)
- Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777)
- Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777)
[w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57)
- Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57)
- Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57)
- Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57)
- Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57)
- Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57)
- Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57)
- Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57)
[w3c/payment-request] Editorial: fixed grammatical errors (#790)
- Re: [w3c/payment-request] Editorial: fixed grammatical errors (#790)
- Re: [w3c/payment-request] Editorial: fixed grammatical errors (#790)
- Re: [w3c/payment-request] Editorial: fixed grammatical errors (#790)
- Re: [w3c/payment-request] Editorial: fixed grammatical errors (#790)
Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789)
- Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789)
- Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789)
- Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789)
- Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789)
- Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789)
- Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789)
- Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789)
- Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789)
- Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789)