public-webpayments-specs@w3.org from January 2019 by author

Adrian Hope-Bailie

• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) (Thursday, 24 January)
• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) (Friday, 18 January)

Anders Rundgren

• Re: [w3c/payment-request] Applying "Detached" JWS Signatures to PaymentRequest (#714) (Friday, 4 January)

Anne van Kesteren

• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Wednesday, 16 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)

Danyao Wang

• [w3c/payment-request] Spec hasEnrolledInstrument (#830) (Wednesday, 30 January)
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) (Wednesday, 30 January)
• Re: [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) (Wednesday, 30 January)
• Re: [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) (Wednesday, 30 January)
• Re: [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) (Wednesday, 30 January)
• Re: [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) (Wednesday, 30 January)
• Re: [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) (Wednesday, 30 January)
• Re: [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) (Wednesday, 30 January)
• [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) (Tuesday, 29 January)
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) (Monday, 28 January)
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) (Wednesday, 23 January)
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) (Wednesday, 23 January)
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) (Wednesday, 23 January)
• [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) (Tuesday, 22 January)

Domenic Denicola

• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#824) (Wednesday, 30 January)
• Re: [w3c/payment-request] Do .data IDL conversion in constructor (#829) (Wednesday, 30 January)
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) (Monday, 28 January)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Thursday, 24 January)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Thursday, 24 January)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Thursday, 24 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Thursday, 24 January)
• Re: [w3c/payment-request] Remove regionCode attribute (#823) (Thursday, 24 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)

Ian Clelland

• Re: [w3c/payment-request] Integrate with Feature Policy (#822) (Wednesday, 30 January)
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) (Friday, 25 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)

ianbjacobs

• Re: [w3c/payment-request] Spec hasEnrolledInstrument (#830) (Thursday, 31 January)
• [w3c/payment-handler] Rename canMakePayment* hasEnrolledInstrument (#332) (Wednesday, 30 January)
• Re: [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) (Wednesday, 30 January)
• Re: [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) (Tuesday, 29 January)
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) (Tuesday, 29 January)
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) (Tuesday, 29 January)
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) (Friday, 25 January)
• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) (Friday, 25 January)
• Re: [w3c/payment-request] Remove regionCode attribute (#823) (Thursday, 24 January)
• Re: [w3c/payment-request] Editorial: reworded examples, nits (#827) (Tuesday, 22 January)
• Re: [w3c/payment-request] Editorial: reworded examples, nits (#827) (Tuesday, 22 January)
• Re: [w3c/payment-request] Remove PaymentAddress' regionCode attribute (#823) (Thursday, 17 January)
• [w3c/payment-method-id] Json update (#59) (Thursday, 17 January)
• [w3c/payment-method-basic-card] Removed deprecated shortname field (#66) (Thursday, 17 January)
• [w3c/payment-request] Updated per Dom Hazael-Massieux (#826) (Thursday, 17 January)
• Re: [w3c/payment-handler] updated per DHM (#329) (Thursday, 17 January)
• [w3c/payment-handler] updated per DHM (#329) (Thursday, 17 January)
• Re: [w3c/payment-request] Clarify retry() when errorFields are not passed (#825) (Wednesday, 16 January)
• Re: [w3c/payment-request] Clarify retry() when errorFields are not passed (#825) (Wednesday, 16 January)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Wednesday, 16 January)
• [w3c/payment-method-id] Fix link to implementation report (#58) (Wednesday, 16 January)
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) (Wednesday, 16 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) (Tuesday, 8 January)

Marcos Cáceres

• Re: [w3c/payment-request] Providing an `AbortSignal` instead of calling .abort() (#757) (Thursday, 31 January)
• Re: [w3c/payment-request] Do .data IDL conversion in constructor (#829) (Thursday, 31 January)
• Re: [w3c/payment-request] Do .data IDL conversion in constructor (#829) (Thursday, 31 January)
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) (Thursday, 31 January)
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) (Thursday, 31 January)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Thursday, 31 January)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#824) (Thursday, 31 January)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#824) (Thursday, 31 January)
• Re: [w3c/payment-request] Spec hasEnrolledInstrument (#830) (Thursday, 31 January)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#824) (Wednesday, 30 January)
• [w3c/payment-request] Do .data IDL conversion in constructor (#829) (Tuesday, 29 January)
• Re: [w3c/payment-request] Do .data IDL conversion in constructor (#828) (Tuesday, 29 January)
• [w3c/payment-request] Modifiers (#828) (Tuesday, 29 January)
• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) (Tuesday, 29 January)
• Re: [w3c/payment-request] Integration with Feature Policy (#600) (Tuesday, 29 January)
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) (Tuesday, 29 January)
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) (Tuesday, 29 January)
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) (Tuesday, 29 January)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Tuesday, 29 January)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Tuesday, 29 January)
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) (Tuesday, 29 January)
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) (Friday, 25 January)
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) (Friday, 25 January)
• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) (Thursday, 24 January)
• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) (Thursday, 24 January)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Thursday, 24 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Thursday, 24 January)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Thursday, 24 January)
• Re: [w3c/payment-request] Remove regionCode attribute (#823) (Thursday, 24 January)
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) (Thursday, 24 January)
• Re: [w3c/payment-request] Editorial: reworded examples, nits (#827) (Tuesday, 22 January)
• Re: [w3c/payment-request] Editorial: reworded examples, nits (#827) (Tuesday, 22 January)
• Re: [w3c/payment-request] Editorial: reworded examples, nits (#827) (Tuesday, 22 January)
• Re: [w3c/payment-request] Editorial: reworded examples, nits (#827) (Tuesday, 22 January)
• Re: [w3c/payment-request] Editorial: reworded examples, nits (#827) (Tuesday, 22 January)
• [w3c/payment-request] Editorial: reworded examples, nits (#827) (Tuesday, 22 January)
• Re: [w3c/payment-request] Remove regionCode attribute (doesn't spark joy) (#823) (Tuesday, 22 January)
• Re: [w3c/payment-request] Remove regionCode attribute (doesn't spark joy) (#823) (Tuesday, 22 January)
• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) (Tuesday, 22 January)
• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) (Tuesday, 22 January)
• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) (Tuesday, 22 January)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Monday, 21 January)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Monday, 21 January)
• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) (Friday, 18 January)
• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) (Friday, 18 January)
• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) (Friday, 18 January)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Friday, 18 January)
• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) (Thursday, 17 January)
• Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) (Thursday, 17 January)
• Re: [w3c/payment-request] Remove PaymentAddress' regionCode attribute (#823) (Thursday, 17 January)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Thursday, 17 January)
• Re: [w3c/payment-request] Clarify retry() when errorFields are not passed (#825) (Thursday, 17 January)
• Re: [w3c/payment-request] Clarify retry() when errorFields are not passed (#825) (Thursday, 17 January)
• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) (Thursday, 17 January)
• Re: [w3c/payment-request] Clarification question for `show()` algorithm (#820) (Thursday, 17 January)
• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) (Thursday, 17 January)
• Re: [w3c/payment-method-id] Prepare for Proposed Recommendation (#56) (Thursday, 17 January)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Thursday, 17 January)
• Re: [w3c/payment-method-id] Generate an implementation report (#54) (Thursday, 17 January)
• Re: [w3c/payment-method-id] Fix link to implementation report (#58) (Thursday, 17 January)
• Re: [w3c/payment-method-id] Fix link to implementation report (#58) (Thursday, 17 January)
• Re: [w3c/payment-method-id] chore(w3c): small update to w3c json (#59) (Thursday, 17 January)
• Re: [w3c/payment-method-id] chore(w3c): small update to w3c json (#59) (Thursday, 17 January)
• Re: [w3c/payment-request] Updated per Dom Hazael-Massieux (#826) (Thursday, 17 January)
• Re: [w3c/payment-request] Updated per Dom Hazael-Massieux (#826) (Thursday, 17 January)
• Re: [w3c/payment-request] Updated per Dom Hazael-Massieux (#826) (Thursday, 17 January)
• Re: [w3c/payment-method-basic-card] Removed deprecated shortname field (#66) (Thursday, 17 January)
• Re: [w3c/payment-method-basic-card] Removed deprecated shortname field (#66) (Thursday, 17 January)
• Re: [w3c/payment-method-basic-card] Removed deprecated shortname field (#66) (Thursday, 17 January)
• Re: [w3c/payment-request] Clarify retry() when errorFields are not passed (#825) (Wednesday, 16 January)
• Re: [w3c/payment-request] Clarify retry() when errorFields are not passed (#825) (Wednesday, 16 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Wednesday, 16 January)
• Re: [w3c/payment-request] test suite that checks whether shipping options can be updated (#791) (Wednesday, 16 January)
• Re: [w3c/payment-request] test suite that checks whether shipping options can be updated (#791) (Wednesday, 16 January)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Wednesday, 16 January)
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) (Wednesday, 16 January)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Wednesday, 16 January)
• [w3c/payment-request] Clarify retry() when errorFields are not passed (#825) (Wednesday, 16 January)
• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) (Wednesday, 16 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Wednesday, 16 January)
• Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) (Wednesday, 16 January)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Wednesday, 16 January)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Wednesday, 16 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Wednesday, 16 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Wednesday, 16 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Wednesday, 16 January)
• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) (Wednesday, 16 January)
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) (Wednesday, 16 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#824) (Tuesday, 15 January)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#824) (Tuesday, 15 January)
• [w3c/payment-request] Define handling of multiple applicable modifiers (#824) (Tuesday, 15 January)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Tuesday, 15 January)
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) (Tuesday, 15 January)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Tuesday, 15 January)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Tuesday, 15 January)
• [w3c/payment-request] Remove PaymentAddress' regionCode attribute (#823) (Tuesday, 15 January)
• [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) (Tuesday, 15 January)
• Re: [w3c/payment-request] Confirm tests and specs align (#779) (Monday, 14 January)
• Re: [w3c/payment-request] Confirm tests and specs align (#779) (Monday, 14 January)
• Re: [w3c/payment-request] Support for language the form is served (#819) (Monday, 14 January)
• Re: [w3c/payment-request] Support for language the form is served (#819) (Monday, 14 January)
• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) (Friday, 11 January)
• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) (Friday, 11 January)
• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) (Friday, 11 January)
• [w3c/payment-request] fix: close request if sheet is showing (#821) (Friday, 11 January)
• Re: [w3c/payment-request] Clarification question for `show()` algorithm (#820) (Friday, 11 January)
• Re: [w3c/payment-request] Clarification question for `show()` algorithm (#820) (Thursday, 10 January)
• Re: [w3c/payment-request] Clarification question for `show()` algorithm (#820) (Thursday, 10 January)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Thursday, 10 January)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) (Thursday, 10 January)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) (Thursday, 10 January)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) (Thursday, 10 January)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) (Thursday, 10 January)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Wednesday, 9 January)
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) (Tuesday, 8 January)
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) (Tuesday, 8 January)

Rouslan Solomakhin

• Re: [w3c/payment-request] Spec hasEnrolledInstrument (#830) (Thursday, 31 January)
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) (Tuesday, 29 January)
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) (Monday, 28 January)
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) (Thursday, 24 January)
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) (Wednesday, 23 January)
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) (Wednesday, 23 January)
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) (Wednesday, 23 January)
• Re: [w3c/payment-request] Remove PaymentAddress' regionCode attribute (#823) (Thursday, 17 January)
• Re: [w3c/payment-request] Clarify retry() when errorFields are not passed (#825) (Wednesday, 16 January)
• Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) (Tuesday, 15 January)
• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) (Tuesday, 15 January)
• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) (Tuesday, 15 January)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Tuesday, 15 January)
• Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) (Tuesday, 15 January)
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) (Tuesday, 15 January)

Zouhir ⚡️

• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) (Tuesday, 15 January)
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) (Tuesday, 15 January)

Last message date: Thursday, 31 January 2019 17:51:50 UTC