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

Thursday, 31 January 2019

• Re: [w3c/payment-request] Spec hasEnrolledInstrument (#830) ianbjacobs
• Re: [w3c/payment-request] Spec hasEnrolledInstrument (#830) Rouslan Solomakhin
• Re: [w3c/payment-request] Providing an `AbortSignal` instead of calling .abort() (#757) Marcos Cáceres
• Re: [w3c/payment-request] Do .data IDL conversion in constructor (#829) Marcos Cáceres
• Re: [w3c/payment-request] Do .data IDL conversion in constructor (#829) Marcos Cáceres
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) Marcos Cáceres
• Re: [w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753) Marcos Cáceres
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Marcos Cáceres
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#824) Marcos Cáceres
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#824) Marcos Cáceres
• Re: [w3c/payment-request] Spec hasEnrolledInstrument (#830) Marcos Cáceres

Wednesday, 30 January 2019

• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#824) Marcos Cáceres
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) Ian Clelland
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#824) Domenic Denicola
• Re: [w3c/payment-request] Do .data IDL conversion in constructor (#829) Domenic Denicola
• [w3c/payment-request] Spec hasEnrolledInstrument (#830) Danyao Wang
• [w3c/payment-handler] Rename canMakePayment* hasEnrolledInstrument (#332) ianbjacobs
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) Danyao Wang
• Re: [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) Danyao Wang
• Re: [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) ianbjacobs
• Re: [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) Danyao Wang
• Re: [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) Danyao Wang
• Re: [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) Danyao Wang
• Re: [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) Danyao Wang
• Re: [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) Danyao Wang

Tuesday, 29 January 2019

• Re: [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) ianbjacobs
• [w3c/payment-handler] Add a privacy consideration note for issue #330. (#331) Danyao Wang
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) ianbjacobs
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) Rouslan Solomakhin
• [w3c/payment-request] Do .data IDL conversion in constructor (#829) Marcos Cáceres
• Re: [w3c/payment-request] Do .data IDL conversion in constructor (#828) Marcos Cáceres
• [w3c/payment-request] Modifiers (#828) Marcos Cáceres
• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) Marcos Cáceres
• Re: [w3c/payment-request] Integration with Feature Policy (#600) Marcos Cáceres
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) Marcos Cáceres
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) Marcos Cáceres
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) Marcos Cáceres
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Marcos Cáceres
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Marcos Cáceres
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) Marcos Cáceres
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) ianbjacobs

Monday, 28 January 2019

• Re: [w3c/payment-request] Integrate with Feature Policy (#822) Domenic Denicola
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) Danyao Wang
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) Rouslan Solomakhin

Friday, 25 January 2019

• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) ianbjacobs
• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) ianbjacobs
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) Ian Clelland
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) Marcos Cáceres
• Re: [w3c/payment-request] Integrate with Feature Policy (#822) Marcos Cáceres

Thursday, 24 January 2019

• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) Marcos Cáceres
• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) Marcos Cáceres
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Domenic Denicola
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Marcos Cáceres
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Domenic Denicola
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Marcos Cáceres
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Domenic Denicola
• Re: [w3c/payment-request] Remove regionCode attribute (#823) Marcos Cáceres
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Domenic Denicola
• Re: [w3c/payment-request] Remove regionCode attribute (#823) Domenic Denicola
• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) Adrian Hope-Bailie
• Re: [w3c/payment-request] Remove regionCode attribute (#823) ianbjacobs
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) Rouslan Solomakhin

Wednesday, 23 January 2019

• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) Danyao Wang
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) Rouslan Solomakhin
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) Danyao Wang
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) Rouslan Solomakhin
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) Danyao Wang
• Re: [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) Rouslan Solomakhin

Tuesday, 22 January 2019

• [w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330) Danyao Wang
• Re: [w3c/payment-request] Editorial: reworded examples, nits (#827) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: reworded examples, nits (#827) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: reworded examples, nits (#827) ianbjacobs
• Re: [w3c/payment-request] Editorial: reworded examples, nits (#827) ianbjacobs
• Re: [w3c/payment-request] Editorial: reworded examples, nits (#827) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: reworded examples, nits (#827) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: reworded examples, nits (#827) Marcos Cáceres
• [w3c/payment-request] Editorial: reworded examples, nits (#827) Marcos Cáceres
• Re: [w3c/payment-request] Remove regionCode attribute (doesn't spark joy) (#823) Marcos Cáceres
• Re: [w3c/payment-request] Remove regionCode attribute (doesn't spark joy) (#823) Marcos Cáceres
• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Marcos Cáceres
• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Marcos Cáceres
• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) Marcos Cáceres

Monday, 21 January 2019

• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Marcos Cáceres
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Marcos Cáceres

Friday, 18 January 2019

• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) Marcos Cáceres
• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) Adrian Hope-Bailie
• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) Marcos Cáceres
• Re: [w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817) Marcos Cáceres
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres

Thursday, 17 January 2019

• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) Marcos Cáceres
• Re: [w3c/payment-request] Remove PaymentAddress' regionCode attribute (#823) Rouslan Solomakhin
• Re: [w3c/payment-request] Remove PaymentAddress' regionCode attribute (#823) ianbjacobs
• Re: [w3c/payment-request] Remove PaymentAddress' regionCode attribute (#823) Marcos Cáceres
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Marcos Cáceres
• Re: [w3c/payment-request] Clarify retry() when errorFields are not passed (#825) Marcos Cáceres
• Re: [w3c/payment-request] Clarify retry() when errorFields are not passed (#825) Marcos Cáceres
• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) Marcos Cáceres
• Re: [w3c/payment-request] Clarification question for `show()` algorithm (#820) Marcos Cáceres
• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) Marcos Cáceres
• Re: [w3c/payment-method-id] Prepare for Proposed Recommendation (#56) Marcos Cáceres
• Re: [w3c/payment-method-id] Generate an implementation report (#54) Marcos Cáceres
• Re: [w3c/payment-method-id] Generate an implementation report (#54) Marcos Cáceres
• Re: [w3c/payment-method-id] Fix link to implementation report (#58) Marcos Cáceres
• Re: [w3c/payment-method-id] Fix link to implementation report (#58) Marcos Cáceres
• Re: [w3c/payment-method-id] chore(w3c): small update to w3c json (#59) Marcos Cáceres
• Re: [w3c/payment-method-id] chore(w3c): small update to w3c json (#59) Marcos Cáceres
• Re: [w3c/payment-request] Updated per Dom Hazael-Massieux (#826) Marcos Cáceres
• Re: [w3c/payment-request] Updated per Dom Hazael-Massieux (#826) Marcos Cáceres
• Re: [w3c/payment-request] Updated per Dom Hazael-Massieux (#826) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Removed deprecated shortname field (#66) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Removed deprecated shortname field (#66) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Removed deprecated shortname field (#66) Marcos Cáceres
• [w3c/payment-method-id] Json update (#59) ianbjacobs
• [w3c/payment-method-basic-card] Removed deprecated shortname field (#66) ianbjacobs
• [w3c/payment-request] Updated per Dom Hazael-Massieux (#826) ianbjacobs
• Re: [w3c/payment-handler] updated per DHM (#329) ianbjacobs
• [w3c/payment-handler] updated per DHM (#329) ianbjacobs

Wednesday, 16 January 2019

• Re: [w3c/payment-request] Clarify retry() when errorFields are not passed (#825) Marcos Cáceres
• Re: [w3c/payment-request] Clarify retry() when errorFields are not passed (#825) Marcos Cáceres
• Re: [w3c/payment-request] Clarify retry() when errorFields are not passed (#825) ianbjacobs
• Re: [w3c/payment-request] Clarify retry() when errorFields are not passed (#825) ianbjacobs
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) ianbjacobs
• [w3c/payment-method-id] Fix link to implementation report (#58) ianbjacobs
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) ianbjacobs
• Re: [w3c/payment-request] Clarify retry() when errorFields are not passed (#825) Rouslan Solomakhin
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Anne van Kesteren
• 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
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) Marcos Cáceres
• Re: [w3c/payment-request] Some clarifications with Payment Request API (#774) Marcos Cáceres
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Marcos Cáceres
• [w3c/payment-request] Clarify retry() when errorFields are not passed (#825) Marcos Cáceres
• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres
• Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) Marcos Cáceres
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres
• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) Marcos Cáceres
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) Marcos Cáceres

Tuesday, 15 January 2019

• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) Zouhir ⚡️
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Ian Clelland
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Domenic Denicola
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) Zouhir ⚡️
• Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) Rouslan Solomakhin
• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) Rouslan Solomakhin
• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) Rouslan Solomakhin
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) Rouslan Solomakhin
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) Rouslan Solomakhin
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Domenic Denicola
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) ianbjacobs
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) ianbjacobs
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) ianbjacobs
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Anne van Kesteren
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#824) Marcos Cáceres
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#824) Marcos Cáceres
• [w3c/payment-request] Define handling of multiple applicable modifiers (#824) Marcos Cáceres
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Marcos Cáceres
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) Marcos Cáceres
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Marcos Cáceres
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Marcos Cáceres
• [w3c/payment-request] Remove PaymentAddress' regionCode attribute (#823) Marcos Cáceres
• [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: relationship to Feature Policy spec (#822) Marcos Cáceres

Monday, 14 January 2019

• Re: [w3c/payment-request] Confirm tests and specs align (#779) Marcos Cáceres
• Re: [w3c/payment-request] Confirm tests and specs align (#779) Marcos Cáceres
• Re: [w3c/payment-request] Support for language the form is served (#819) Marcos Cáceres
• Re: [w3c/payment-request] Support for language the form is served (#819) Marcos Cáceres

Friday, 11 January 2019

• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) Marcos Cáceres
• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) Marcos Cáceres
• Re: [w3c/payment-request] fix: close request if sheet is showing (#821) Marcos Cáceres
• [w3c/payment-request] fix: close request if sheet is showing (#821) Marcos Cáceres
• Re: [w3c/payment-request] Clarification question for `show()` algorithm (#820) Marcos Cáceres

Thursday, 10 January 2019

• Re: [w3c/payment-request] Clarification question for `show()` algorithm (#820) Marcos Cáceres
• Re: [w3c/payment-request] Clarification question for `show()` algorithm (#820) Marcos Cáceres
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) Marcos Cáceres
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) Marcos Cáceres
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) Marcos Cáceres
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) Marcos Cáceres

Wednesday, 9 January 2019

• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres

Tuesday, 8 January 2019

• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) ianbjacobs
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) Marcos Cáceres
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) Marcos Cáceres

Friday, 4 January 2019

• Re: [w3c/payment-request] Applying "Detached" JWS Signatures to PaymentRequest (#714) Anders Rundgren

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