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

Monday, 29 October 2018

• Re: [w3c/payment-request] maxprofs (#803) Marcos Cáceres
• Re: [w3c/payment-request] maxprofs (#803) Marcos Cáceres
• Re: [w3c/payment-request] maxprofs (#803) Oscar Gomez
• Re: [w3c/payment-request] maxprofs (#803) Oscar Gomez
• [w3c/payment-request] maxprofs (#803) Oscar Gomez

Friday, 26 October 2018

• Re: [w3c/payment-method-basic-card] Drop supportedTypes? (#59) ianbjacobs
• Re: [w3c/payment-request] Follow up on APA Comments on Web Payments FPWDs (#735) ianbjacobs
• Re: [w3c/payment-request] Added section and paragraph on accessibility considerations (#802) Marcos Cáceres
• Re: [w3c/payment-request] Added section and paragraph on accessibility considerations (#802) Marcos Cáceres
• [w3c/payment-request] Added section and paragraph on accessibility considerations (#802) ianbjacobs

Thursday, 25 October 2018

• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Matt N.

Wednesday, 24 October 2018

• [w3c/payment-request] Way of detecting if can make payment (#801) Marcos Cáceres
• [w3c/payment-request] Meaning of canMakePayment() (#800) Marcos Cáceres
• Re: [w3c/payment-request] Consider specifying a testing IDL for a mock payment UI (#799) aestes
• Re: [w3c/payment-request] Consider specifying a testing IDL for a mock payment UI (#799) ianbjacobs
• [w3c/payment-request] Consider specifying a testing IDL for a mock payment UI (#799) aestes
• Re: [w3c/payment-request] Make Basic Card Payment Method Spec an informative reference (#798) ianbjacobs
• Re: [w3c/payment-request] Make Basic Card Payment Method Spec an informative reference (#798) Marcos Cáceres
• Re: [w3c/payment-request] Make Basic Card Payment Method Spec an informative reference (#798) Marcos Cáceres
• Re: [w3c/payment-request] Make Basic Card Payment Method Spec an informative reference (#798) ianbjacobs
• [w3c/payment-request] Make Basic Card Payment Method Spec an informative reference (#798) Adrian Hope-Bailie

Tuesday, 23 October 2018

• [w3c/webpayments-methods-tokenization] Should tpans be captured? (#53) rvm4

Monday, 22 October 2018

• [w3c/payment-request] Treat scroll as a user gesture for PaymentRequest.show() (#797) Danyao Wang
• [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) aestes

Thursday, 18 October 2018

• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) ianbjacobs
• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) Adrian Hope-Bailie
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) Marcos Cáceres
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Marcos Cáceres
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Marcos Cáceres
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Rouslan Solomakhin
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Rouslan Solomakhin
• Re: [w3c/payment-request] Remove PaymentAddress' languageCode (#765) Marcos Cáceres
• Re: [w3c/payment-request] Remove PaymentItem.type (#794) Marcos Cáceres
• Re: [w3c/payment-request] Remove PaymentItem.type (#794) Marcos Cáceres
• Re: [w3c/payment-request] Remove PaymentItem.type (#794) ianbjacobs
• Re: [w3c/payment-request] Sensible defaults for dictionary members (#780) Marcos Cáceres

Wednesday, 17 October 2018

• Re: [w3c/payment-handler] Simplifying functional event handling (#305) ianbjacobs
• Re: [w3c/payment-handler] Simplifying functional event handling (#305) ianbjacobs
• Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) ianbjacobs
• Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) Rouslan Solomakhin
• Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) ianbjacobs
• Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) Rouslan Solomakhin
• Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) Rouslan Solomakhin
• Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) ianbjacobs
• Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) Rouslan Solomakhin
• Re: [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795) Marcos Cáceres
• Re: [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795) aestes
• Re: [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795) aestes
• Re: [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795) aestes
• [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795) aestes

Tuesday, 16 October 2018

• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) ianbjacobs
• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) Adrian Hope-Bailie

Friday, 12 October 2018

• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) Marcos Cáceres

Thursday, 11 October 2018

• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) aestes

Wednesday, 10 October 2018

• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) Rouslan Solomakhin
• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) Marcos Cáceres
• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) Marcos Cáceres

Tuesday, 9 October 2018

• Re: [w3c/payment-request] Remove PaymentItem.type (#794) ianbjacobs
• Re: [w3c/payment-request] Remove PaymentItem.type (#794) ianbjacobs
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) aestes
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Marcos Cáceres
• [w3c/payment-request] Remove PaymentItem.type (#794) Marcos Cáceres

Monday, 8 October 2018

• Re: [w3c/payment-handler] Simplifying functional event handling (#305) ianbjacobs
• Re: [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) ianbjacobs
• [w3c/payment-handler] Removed conflicts from Jake Archibald pull request (#327) ianbjacobs

Friday, 5 October 2018

• Re: [w3c/payment-request] test suite that checks whether shipping options can be updated (#791) Adi

Thursday, 4 October 2018

• Re: [w3c/payment-request] Should we validate nonsense payer error properties? (#793) aestes
• Re: [w3c/webpayments-methods-tokenization] Better orient the reader (#51) Peter Saint-Andre
• Re: [w3c/webpayments-methods-tokenization] Better orient the reader (#51) Peter Saint-Andre
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Matt N.
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Marcos Cáceres

Wednesday, 3 October 2018

• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Rouslan Solomakhin
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Marcos Cáceres
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) aestes
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Marcos Cáceres
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Rouslan Solomakhin
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Marcos Cáceres
• Re: [w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249) ianbjacobs
• Re: [w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249) Rouslan Solomakhin
• Re: [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248) Rouslan Solomakhin
• Re: [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248) Rouslan Solomakhin
• Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) Rouslan Solomakhin
• Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223) Rouslan Solomakhin
• Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) Rouslan Solomakhin
• Re: [w3c/payment-request] Should we validate nonsense payer error properties? (#793) Rouslan Solomakhin
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Rouslan Solomakhin
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Marcos Cáceres
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Matt N.
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Marcos Cáceres
• Re: [w3c/payment-request] Should we validate nonsense payer error properties? (#793) Marcos Cáceres
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Jinho Bang
• Re: [w3c/payment-request] Should we validate nonsense payer error properties? (#793) Jinho Bang
• Re: [w3c/payment-request] test suite that checks whether shipping options can be updated (#791) Marcos Cáceres
• Re: [w3c/payment-request] test suite that checks whether shipping options can be updated (#791) Marcos Cáceres

Tuesday, 2 October 2018

• [w3c/payment-request] Should we validate nonsense payer error properties? (#793) Marcos Cáceres
• [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Drop supportedTypes? (#59) Matt Saxon
• Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) Jinho Bang
• Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) Jinho Bang
• Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223) Rouslan Solomakhin
• Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223) Jinho Bang
• [w3c/payment-request] test suite that checks whether shipping options can be updated (#791) Adi
• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) ianbjacobs
• Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223) ianbjacobs
• Re: [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248) ianbjacobs
• Re: [w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249) ianbjacobs
• Re: [w3c/payment-request] Support requesting billing address (#749) Marcos Cáceres
• Re: [w3c/payment-request] Rename `PayerErrorFields` to be like `AddressErrors` and `BasicCardErrors` (#782) Marcos Cáceres
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) Marcos Cáceres
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) Marcos Cáceres
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) Marcos Cáceres
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) Akansha
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Editorial: Fixed grammatical error and link to PaymentRequest interface (#61) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Editorial: Fixed grammatical error and link to PaymentRequest interface (#61) Marcos Cáceres
• [w3c/payment-method-basic-card] Editorial: Fixed grammatical error and link to PaymentRequest interface (#61) Wonsuk Lee
• Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57) Marcos Cáceres
• Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57) Marcos Cáceres
• Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57) Marcos Cáceres

Monday, 1 October 2018

• Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57) Wonsuk Lee
• Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57) Wonsuk Lee
• Re: [w3c/payment-request] To address branded button issues and improve privacy, add browser support for payment method selection before the sheet (#777) Adrian Hope-Bailie
• Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57) Marcos Cáceres
• Re: [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57) Marcos Cáceres
• [w3c/payment-method-id] Editorial: Fixed duplication of url and spec name to sync with linked doc (#57) Wonsuk Lee
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) Akansha
• Re: [w3c/payment-request] Editorial: fixed grammatical errors (#790) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: fixed grammatical errors (#790) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: fixed grammatical errors (#790) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: fixed grammatical errors (#790) Marcos Cáceres
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) Jinho Bang
• [w3c/payment-request] Editorial: fixed grammatical errors (#790) Wonsuk Lee
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) Marcos Cáceres
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) Marcos Cáceres
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) Marcos Cáceres
• Re: [w3c/payment-request] Issue #782 - Renames PayerErrorFields to PayerErrors (#789) Marcos Cáceres

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