public-webpayments-specs@w3.org from November 2017 by date

Thursday, 30 November 2017

• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Jenan Wise
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Rouslan Solomakhin
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Ade Bateman
• Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Adam Solove
• Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Rouslan Solomakhin
• Re: [w3c/payment-handler] fix: PaymentInstruments.get not exceptional (#231) Rouslan Solomakhin
• Re: [w3c/payment-handler] PaymentInstruments .set() and icons (#233) Rouslan Solomakhin
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Rouslan Solomakhin
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Rouslan Solomakhin
• Re: [w3c/payment-handler] User consent and permissions (#239) Rouslan Solomakhin
• Re: [w3c/payment-handler] Remove 'Origin and Instrument Display for Selection' sections (#229) Adrian Hope-Bailie
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Rouslan Solomakhin
• Re: [w3c/payment-handler] Editorial: trim/relocate conformance (#226) Adrian Hope-Bailie
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Adrian Hope-Bailie
• Re: [w3c/payment-handler] User consent and permissions (#239) Adrian Hope-Bailie
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Jinho Bang
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Anne van Kesteren
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Marcos Cáceres
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Anne van Kesteren
• Re: [w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22) Anders Rundgren
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Marcos Cáceres
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Marcos Cáceres
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Marcos Cáceres
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Jenan Wise
• Re: [w3c/payment-handler] PaymentInstruments .set() and icons (#233) Marcos Cáceres
• Re: [w3c/payment-handler] fix: PaymentInstruments.get not exceptional (#231) Marcos Cáceres
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Marcos Cáceres
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) michelle
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Marcos Cáceres
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Marcos Cáceres
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Andre Lyver
• Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Marcos Cáceres
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) michelle
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Jenan Wise
• Re: [w3c/payment-request] Should PaymentItems have a type? (#163) michelle
• Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Marcos Cáceres
• Re: [w3c/payment-request] Should PaymentItems have a type? (#163) michelle
• Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Marcos Cáceres
• Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Marcos Cáceres

Wednesday, 29 November 2017

• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Marcos Cáceres
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Ade Bateman
• Re: [w3c/payment-method-basic-card] fix: define how to set billingAddress (closes #44) (#45) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] When creating the billing address, hook into construction of payment address algo from payment request (#44) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] fix: define how to set billingAddress (closes #44) (#45) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] fix: define how to set billingAddress (closes #44) (#45) Rouslan Solomakhin
• Re: [w3c/payment-handler] User consent and permissions (#239) Rouslan Solomakhin
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Rouslan Solomakhin
• Re: [w3c/payment-handler] fix: PaymentInstruments.get not exceptional (#231) Rouslan Solomakhin
• Re: [w3c/payment-handler] Trying to get a non-existing value is not exceptional (#230) Rouslan Solomakhin
• Re: [w3c/payment-handler] User consent and permissions (#239) Rouslan Solomakhin
• Re: [w3c/payment-handler] User consent and permissions (#239) Jinho Bang
• [w3c/payment-handler] Just-in-time payment handler install (#240) Rouslan Solomakhin
• Re: [w3c/payment-handler] User consent and permissions (#239) Rouslan Solomakhin
• Re: [w3c/payment-handler] User consent and permissions (#239) ianbjacobs
• [w3c/payment-handler] User consent and permissions (#239) Rouslan Solomakhin
• Re: [w3c/payment-handler] "Convert image objects" trashes all images (#235) Rouslan Solomakhin
• Re: [w3c/payment-handler] PaymentInstruments .set() and icons (#233) Rouslan Solomakhin
• Re: [w3c/payment-handler] fix: PaymentInstruments.get not exceptional (#231) Rouslan Solomakhin
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Mike West
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Marcos Cáceres
• [w3c/payment-handler] ImageObjects can now reference ImageResource (#238) Marcos Cáceres
• Re: [w3c/payment-handler] fix: PaymentInstruments.get not exceptional (#231) Marcos Cáceres
• Re: [w3c/payment-handler] Remove 'Origin and Instrument Display for Selection' sections (#229) Marcos Cáceres
• Re: [w3c/payment-handler] Editorial: trim introduction (#227) Marcos Cáceres
• Re: [w3c/payment-handler] Editorial: trim/relocate conformance (#226) Marcos Cáceres
• Re: [w3c/payment-handler] Editorial: small fixes, redundancies (#228) Marcos Cáceres
• Re: [w3c/payment-handler] Editorial: trim/relocate conformance (#226) Marcos Cáceres
• Re: [w3c/payment-handler] Editorial: trim/relocate conformance (#226) Marcos Cáceres
• Re: [w3c/payment-handler] Editorial: Simplify abstract (#225) Marcos Cáceres

Tuesday, 28 November 2017

• Re: [w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22) KJM
• Re: [w3c/payment-handler] PaymentInstruments .set() and icons (#233) Marcos Cáceres
• Re: [w3c/payment-handler] "Convert image objects" trashes all images (#235) Marcos Cáceres
• Re: [w3c/payment-handler] Editorial: Simplify abstract (#225) Adrian Hope-Bailie
• Re: [w3c/payment-handler] Editorial: trim/relocate conformance (#226) Adrian Hope-Bailie
• Re: [w3c/payment-handler] Editorial: trim introduction (#227) Adrian Hope-Bailie
• Re: [w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22) mattsaxon
• Re: [w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22) ianbjacobs
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Dave Longley
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Anne van Kesteren
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Dave Longley
• Re: [w3c/payment-handler] PaymentInstruments .set() and icons (#233) Rouslan Solomakhin
• Re: [w3c/payment-handler] "Convert image objects" trashes all images (#235) Rouslan Solomakhin
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Anne van Kesteren
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Jinho Bang
• Re: [w3c/payment-handler] Editorial: small fixes, redundancies (#228) Jinho Bang
• Re: [w3c/payment-handler] Remove 'Origin and Instrument Display for Selection' sections (#229) Jinho Bang
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Anne van Kesteren
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Mike West
• [w3c/payment-handler] Image fetching does not seem to be defined (#237) Anne van Kesteren
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) Anne van Kesteren
• Re: [w3c/payment-handler] Add AbortPaymentEvent. (#207) Marcos Cáceres
• Re: [w3c/payment-handler] Add AbortPaymentEvent. (#207) Marcos Cáceres
• Re: [w3c/payment-handler] fix: PaymentInstruments.get not exceptional (#231) Marcos Cáceres
• Re: [w3c/payment-handler] Remove 'Origin and Instrument Display for Selection' sections (#229) Marcos Cáceres
• [w3c/payment-handler] What happens when clearing site data? (#236) Marcos Cáceres
• Re: [w3c/payment-handler] fix: PaymentInstruments.get not exceptional (#231) Jinho Bang
• [w3c/payment-handler] "Convert image objects" trashes all images (#235) Marcos Cáceres
• [w3c/payment-handler] retrieving the permission state (#234) Marcos Cáceres
• [w3c/payment-handler] PaymentInstruments .set() and icons (#233) Marcos Cáceres
• [w3c/payment-handler] PaymentInstruments' "the collection" needs an internal slot. (#232) Marcos Cáceres
• [w3c/payment-handler] fix: PaymentInstruments.get not exceptional (#231) Marcos Cáceres
• Re: [w3c/payment-handler] Trying to get a non-existing value is not exceptional (#230) Marcos Cáceres
• [w3c/payment-handler] Trying to get a non-existing value is not exceptional (#230) Marcos Cáceres
• [w3c/payment-handler] Remove 'Origin and Instrument Display for Selection' sections (#229) Marcos Cáceres

Monday, 27 November 2017

• [w3c/payment-handler] Editorial: small fixes, redundancies (#228) Marcos Cáceres
• [w3c/payment-handler] Editorial: trim introduction (#227) Marcos Cáceres
• [w3c/payment-handler] Editorial: trim/relocate conformance (#226) Marcos Cáceres
• [w3c/payment-handler] Editorial: Simplify abstract (#225) Marcos Cáceres
• [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) Jinho Bang

Friday, 24 November 2017

• Re: [w3c/payment-request] Require user gesture when `.show()` is called (#651) Anders Rundgren
• [w3c/payment-request] Add localization hint for payment sheet (#656) Marcos Cáceres
• Re: [w3c/payment-request] WIP: add constructor to PaymentAddress (#654) Marcos Cáceres
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Marcos Cáceres
• [w3c/payment-request] show() must be triggered by user activation (#655) Marcos Cáceres
• Re: [w3c/payment-request] Require user gesture when `.show()` is called (#651) Marcos Cáceres

Thursday, 23 November 2017

• Re: [w3c/payment-request] Require user gesture when `.show()` is called (#651) Rouslan Solomakhin
• Re: [w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22) Anders Rundgren
• Re: [w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22) clyouSeeroo
• Re: [w3c/payment-request] Require user gesture when `.show()` is called (#651) Anders Rundgren
• Re: [w3c/payment-request] Require user gesture when `.show()` is called (#651) Anders Rundgren
• Re: [w3c/payment-request] Require user gesture when `.show()` is called (#651) Marcos Cáceres
• Re: [w3c/payment-request] Require user gesture when `.show()` is called (#651) Anders Rundgren
• Re: [w3c/payment-method-basic-card] fix: define how to set billingAddress (closes #44) (#45) Marcos Cáceres
• Re: [w3c/payment-request] Require user gesture when `.show()` is called (#651) Marcos Cáceres
• Re: [w3c/payment-request] should PaymentDetailsUpdate merge with existing data (#649) Marcos Cáceres
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Jenan Wise

Wednesday, 22 November 2017

• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) ianbjacobs
• Re: [w3c/payment-request] should PaymentDetailsUpdate merge with existing data (#649) ianbjacobs
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Marcos Cáceres

Tuesday, 21 November 2017

• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22) Anders Rundgren
• Re: [w3c/payment-request] WIP: add constructor to PaymentAddress (#654) Marcos Cáceres
• Re: [w3c/payment-request] WIP: add constructor to PaymentAddress (#654) Marcos Cáceres

Monday, 20 November 2017

• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Marcos Cáceres
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Marcos Cáceres
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Marcos Cáceres
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223) Rouslan Solomakhin
• Re: [w3c/payment-request] WIP: add constructor to PaymentAddress (#654) Rouslan Solomakhin
• Re: [w3c/payment-request] WIP: add constructor to PaymentAddress (#654) Rouslan Solomakhin
• Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223) Jake Archibald
• Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223) Jinho Bang
• Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223) ianbjacobs
• Re: [w3c/payment-handler] SW registration code unclear/incorrect (#223) Jinho Bang
• [w3c/payment-handler] SW registration code unclear/incorrect (#223) Michael Stillwell
• Re: [w3c/payment-request] WIP: add constructor to PaymentAddress (#654) Marcos Cáceres
• [w3c/payment-request] WIP: add constructor to PaymentAddress (#654) Marcos Cáceres

Sunday, 19 November 2017

• Re: [w3c/payment-request] Make Payment Address construction into its own sub algorithm (#643) Alhammadi3
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) michelle

Saturday, 18 November 2017

• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) Matt N.

Friday, 17 November 2017

• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) Marcos Cáceres
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) Marcos Cáceres

Thursday, 16 November 2017

• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) Rouslan Solomakhin
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) Marcos Cáceres
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) Marc Roberts
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) Marcos Cáceres
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) ianbjacobs
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) michelle
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) Marcos Cáceres
• Re: [w3c/payment-request] Merchant-specified default shipping address (#653) Marcos Cáceres

Wednesday, 15 November 2017

• Re: [w3c/payment-request] Merchant-specified default shipping address (#653) Jenan Wise
• Re: [w3c/payment-request] Merchant-specified default shipping address (#653) Michael[tm] Smith
• Re: [w3c/payment-request] If a card payment fails, should we support exclusion of that card instrument from matching? (#237) ianbjacobs
• Re: [w3c/payment-request] If a card payment fails, should we support exclusion of that card instrument from matching? (#237) ianbjacobs
• Re: [w3c/payment-request] Merchant-specified default shipping address (#653) Marcos Cáceres
• Re: [w3c/payment-request] Merchant-specified default shipping address (#653) Marcos Cáceres

Tuesday, 14 November 2017

• Re: [w3c/payment-request] Merchant-specified default shipping address (#653) Marcos Cáceres
• [w3c/payment-request] Merchant-specified default shipping address (#653) Rouslan Solomakhin
• Re: [w3c/payment-request] Standardize phone number format (#652) Marcos Cáceres
• Re: [w3c/payment-request] Standardize phone number format (#652) Matt N.
• Re: [w3c/payment-request] Standardize phone number format (#652) Marcos Cáceres

Monday, 13 November 2017

• Re: [w3c/payment-handler] Per Tommy, mark him as former editor (#222) ianbjacobs
• Re: [w3c/payment-handler] Per Tommy, mark him as former editor (#222) Rouslan Solomakhin
• [w3c/payment-handler] Per Tommy, mark him as former editor (#222) ianbjacobs

Thursday, 9 November 2017

• Re: [w3c/payment-request] Standardize phone number format (#652) Rouslan Solomakhin

Wednesday, 8 November 2017

• [w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22) mattsaxon
• [w3c/payment-request] Standardize phone number format (#652) michelle
• Re: [w3c/payment-request] Consistent requirement for when `.show()` can be called. (#651) Zach Koch
• Re: [w3c/payment-request] Consistent requirement for when `.show()` can be called. (#651) Rouslan Solomakhin
• Re: [w3c/payment-request] Consistent requirement for when `.show()` can be called. (#651) michelle
• [w3c/payment-request] Consistent requirement for when `.show()` can be called. (#651) michelle
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Rouslan Solomakhin
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` before `.show()` (#639) Jenan Wise
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` before `.show()` (#639) Jenan Wise
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) Rouslan Solomakhin

Tuesday, 7 November 2017

• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) michelle
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) michelle
• [w3c/payment-request] Allow locale to be specified by the developer. (#650) michelle
• [w3c/payment-request] should PaymentDetailsUpdate merge with existing data (#649) Marcos Cáceres
• [w3c/payment-request] redact full shipping address from event until payment response (#648) Marcos Cáceres
• [w3c/payment-request] fine grained error recovery for fields (#647) Marcos Cáceres
• Re: [w3c/payment-request] Merchant validation (#646) Marcos Cáceres
• Re: [w3c/payment-request] Merchant validation (#646) Rouslan Solomakhin
• [w3c/payment-request] Merchant validation (#646) Marcos Cáceres
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) Marcos Cáceres
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) Marcos Cáceres
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) Rouslan Solomakhin
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) michelle
• Re: [w3c/webpayments-methods-tokenization] Should the tokenization task force standardize an interface between payment apps and tokenization service providers? (#14) MasterKeyur
• Re: [w3c/webpayments-methods-tokenization] Where does tokenisation occur in the the flow - and do we care (#16) MasterKeyur
• Re: [w3c/webpayments-methods-tokenization] Need for environment parameter (#19) MasterKeyur
• Re: [w3c/webpayments-methods-tokenization] multiuse flow (#20) MasterKeyur
• Re: [w3c/webpayments-methods-tokenization] What to do if tokenized data looks like basic card data? (#21) MasterKeyur
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) Rouslan Solomakhin
• Re: [w3c/payment-handler] UI testing (#221) ebomcke-ingenico
• Re: [w3c/payment-handler] UI testing (#221) Rouslan Solomakhin
• [w3c/payment-handler] UI testing (#221) ebomcke-ingenico

Monday, 6 November 2017

• Re: [w3c/payment-request] Editorial: define create a PaymentAddress algo (#644) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: define create a PaymentAddress algo (#644) Domenic Denicola
• Re: [w3c/payment-request] Editorial: define create a PaymentAddress algo (#644) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: define create a PaymentAddress algo (#644) Marcos Cáceres
• Re: [w3c/payment-request] Implementation of PaymentAddress.languageCode (#608) James MacWhyte
• Re: [w3c/payment-request] Editorial: define create a PaymentAddress algo (#644) Domenic Denicola
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) michelle
• [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) Jenan Wise

Sunday, 5 November 2017

• [w3c/payment-request] Editorial: define create a PaymentAddress algo (#644) Marcos Cáceres
• [w3c/payment-method-basic-card] fix: define how to set billingAddress (closes #44) (#45) Marcos Cáceres
• [w3c/payment-method-basic-card] When creating the billing address, hook into construction of payment address algo from payment request (#44) Marcos Cáceres
• [w3c/payment-request] Make Payment Address construction into it's own sub algorithm (#643) Marcos Cáceres

Last message date: Thursday, 30 November 2017 23:09:32 UTC