public-webpayments-specs@w3.org from October 2018 by author

Adi

• Re: [w3c/payment-request] test suite that checks whether shipping options can be updated (#791) (Friday, 5 October)
• [w3c/payment-request] test suite that checks whether shipping options can be updated (#791) (Tuesday, 2 October)

Adrian Hope-Bailie

• [w3c/payment-request] Make Basic Card Payment Method Spec an informative reference (#798) (Wednesday, 24 October)
• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) (Thursday, 18 October)
• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) (Tuesday, 16 October)
• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) (Monday, 1 October)

aestes

• Re: [w3c/payment-request] Consider specifying a testing IDL for a mock payment UI (#799) (Wednesday, 24 October)
• [w3c/payment-request] Consider specifying a testing IDL for a mock payment UI (#799) (Wednesday, 24 October)
• [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) (Monday, 22 October)
• Re: [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795) (Wednesday, 17 October)
• Re: [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795) (Wednesday, 17 October)
• Re: [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795) (Wednesday, 17 October)
• [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795) (Wednesday, 17 October)
• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) (Thursday, 11 October)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Tuesday, 9 October)
• Re: [w3c/payment-request] Should we validate nonsense payer error properties? (#793) (Thursday, 4 October)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Wednesday, 3 October)

Akansha

• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) (Tuesday, 2 October)
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) (Monday, 1 October)

Danyao Wang

• [w3c/payment-request] Treat scroll as a user gesture for PaymentRequest.show() (#797) (Monday, 22 October)

ianbjacobs

• Re: [w3c/payment-method-basic-card] Drop supportedTypes? (#59) (Friday, 26 October)
• Re: [w3c/payment-request] Follow up on APA Comments on Web Payments FPWDs (#735) (Friday, 26 October)
• [w3c/payment-request] Added section and paragraph on accessibility considerations (#802) (Friday, 26 October)
• Re: [w3c/payment-request] Consider specifying a testing IDL for a mock payment UI (#799) (Wednesday, 24 October)
• Re: [w3c/payment-request] Make Basic Card Payment Method Spec an informative reference (#798) (Wednesday, 24 October)
• Re: [w3c/payment-request] Make Basic Card Payment Method Spec an informative reference (#798) (Wednesday, 24 October)
• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) (Thursday, 18 October)
• Re: [w3c/payment-request] Remove PaymentItem.type (#794) (Thursday, 18 October)
• Re: [w3c/payment-handler] Simplifying functional event handling (#305) (Wednesday, 17 October)
• Re: [w3c/payment-handler] Simplifying functional event handling (#305) (Wednesday, 17 October)
• Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) (Wednesday, 17 October)
• Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) (Wednesday, 17 October)
• Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) (Wednesday, 17 October)
• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) (Tuesday, 16 October)
• Re: [w3c/payment-request] Remove PaymentItem.type (#794) (Tuesday, 9 October)
• Re: [w3c/payment-request] Remove PaymentItem.type (#794) (Tuesday, 9 October)
• Re: [w3c/payment-handler] Simplifying functional event handling (#305) (Monday, 8 October)
• Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) (Monday, 8 October)
• [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) (Monday, 8 October)
• Re: [w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249) (Wednesday, 3 October)
• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) (Tuesday, 2 October)
• Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223) (Tuesday, 2 October)
• Re: [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248) (Tuesday, 2 October)
• Re: [w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249) (Tuesday, 2 October)

Jinho Bang

• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Wednesday, 3 October)
• Re: [w3c/payment-request] Should we validate nonsense payer error properties? (#793) (Wednesday, 3 October)
• Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) (Tuesday, 2 October)
• Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) (Tuesday, 2 October)
• Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223) (Tuesday, 2 October)
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) (Monday, 1 October)

Marcos Cáceres

• Re: [w3c/payment-request] maxprofs (#803) (Monday, 29 October)
• Re: [w3c/payment-request] maxprofs (#803) (Monday, 29 October)
• Re: [w3c/payment-request] Added section and paragraph on accessibility considerations (#802) (Friday, 26 October)
• Re: [w3c/payment-request] Added section and paragraph on accessibility considerations (#802) (Friday, 26 October)
• [w3c/payment-request] Way of detecting if can make payment (#801) (Wednesday, 24 October)
• [w3c/payment-request] Meaning of canMakePayment() (#800) (Wednesday, 24 October)
• Re: [w3c/payment-request] Make Basic Card Payment Method Spec an informative reference (#798) (Wednesday, 24 October)
• Re: [w3c/payment-request] Make Basic Card Payment Method Spec an informative reference (#798) (Wednesday, 24 October)
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) (Thursday, 18 October)
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) (Thursday, 18 October)
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) (Thursday, 18 October)
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) (Thursday, 18 October)
• Re: [w3c/payment-request] Remove PaymentItem.type (#794) (Thursday, 18 October)
• Re: [w3c/payment-request] Remove PaymentItem.type (#794) (Thursday, 18 October)
• Re: [w3c/payment-request] Sensible defaults for dictionary members (#780) (Thursday, 18 October)
• Re: [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795) (Wednesday, 17 October)
• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) (Friday, 12 October)
• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) (Wednesday, 10 October)
• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) (Wednesday, 10 October)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Tuesday, 9 October)
• [w3c/payment-request] Remove PaymentItem.type (#794) (Tuesday, 9 October)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Thursday, 4 October)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Wednesday, 3 October)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Wednesday, 3 October)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Wednesday, 3 October)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Wednesday, 3 October)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Wednesday, 3 October)
• Re: [w3c/payment-request] Should we validate nonsense payer error properties? (#793) (Wednesday, 3 October)
• Re: [w3c/payment-request] test suite that checks whether shipping options can be updated (#791) (Wednesday, 3 October)
• Re: [w3c/payment-request] test suite that checks whether shipping options can be updated (#791) (Wednesday, 3 October)
• [w3c/payment-request] Should we validate nonsense payer error properties? (#793) (Tuesday, 2 October)
• [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Tuesday, 2 October)
• Re: [w3c/payment-request] Support requesting billing address (#749) (Tuesday, 2 October)
• Re: [w3c/payment-request] Rename `PayerErrorFields` to be like `AddressErrors` and `BasicCardErrors` (#782) (Tuesday, 2 October)
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) (Tuesday, 2 October)
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) (Tuesday, 2 October)
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) (Tuesday, 2 October)
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) (Tuesday, 2 October)
• Re: [w3c/payment-method-basic-card] Editorial: Fixed grammatical error and link to PaymentRequest interface (#61) (Tuesday, 2 October)
• Re: [w3c/payment-method-basic-card] Editorial: Fixed grammatical error and link to PaymentRequest interface (#61) (Tuesday, 2 October)
• Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57) (Tuesday, 2 October)
• Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57) (Tuesday, 2 October)
• Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57) (Tuesday, 2 October)
• Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57) (Monday, 1 October)
• Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57) (Monday, 1 October)
• Re: [w3c/payment-request] Editorial: fixed grammatical errors (#790) (Monday, 1 October)
• Re: [w3c/payment-request] Editorial: fixed grammatical errors (#790) (Monday, 1 October)
• Re: [w3c/payment-request] Editorial: fixed grammatical errors (#790) (Monday, 1 October)
• Re: [w3c/payment-request] Editorial: fixed grammatical errors (#790) (Monday, 1 October)
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) (Monday, 1 October)
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) (Monday, 1 October)
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) (Monday, 1 October)
• Re: [w3c/payment-request] Issue #782 - Renames PayerErrorFields to PayerErrors (#789) (Monday, 1 October)

Matt N.

• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Thursday, 25 October)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Thursday, 4 October)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Wednesday, 3 October)

Matt Saxon

• Re: [w3c/payment-method-basic-card] Drop supportedTypes? (#59) (Tuesday, 2 October)

Oscar Gomez

• Re: [w3c/payment-request] maxprofs (#803) (Monday, 29 October)
• Re: [w3c/payment-request] maxprofs (#803) (Monday, 29 October)
• [w3c/payment-request] maxprofs (#803) (Monday, 29 October)

Peter Saint-Andre

• Re: [w3c/webpayments-methods-tokenization] Better orient the reader (#51) (Thursday, 4 October)
• Re: [w3c/webpayments-methods-tokenization] Better orient the reader (#51) (Thursday, 4 October)

Rouslan Solomakhin

• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) (Thursday, 18 October)
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) (Thursday, 18 October)
• Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) (Wednesday, 17 October)
• Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) (Wednesday, 17 October)
• Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) (Wednesday, 17 October)
• Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) (Wednesday, 17 October)
• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) (Wednesday, 10 October)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Wednesday, 3 October)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Wednesday, 3 October)
• Re: [w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249) (Wednesday, 3 October)
• Re: [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248) (Wednesday, 3 October)
• Re: [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248) (Wednesday, 3 October)
• Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) (Wednesday, 3 October)
• Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223) (Wednesday, 3 October)
• Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) (Wednesday, 3 October)
• Re: [w3c/payment-request] Should we validate nonsense payer error properties? (#793) (Wednesday, 3 October)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Wednesday, 3 October)
• Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223) (Tuesday, 2 October)

rvm4

• [w3c/webpayments-methods-tokenization] Should tpans be captured? (#53) (Tuesday, 23 October)

Wonsuk Lee

• [w3c/payment-method-basic-card] Editorial: Fixed grammatical error and link to PaymentRequest interface (#61) (Tuesday, 2 October)
• Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57) (Monday, 1 October)
• Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57) (Monday, 1 October)
• [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57) (Monday, 1 October)
• [w3c/payment-request] Editorial: fixed grammatical errors (#790) (Monday, 1 October)

Last message date: Monday, 29 October 2018 12:49:50 UTC