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

Friday, 29 December 2017

Re: [w3c/payment-request] Move PMI and Card specs out of repo (94e40c5) jarrenwe26

Wednesday, 27 December 2017

Re: [w3c/payment-request] Add localization hint for payment sheet (#656) jarrenwe26

Saturday, 23 December 2017

Re: [w3c/webpayments-methods-tokenization] Proposal for dealing with Signed and Unsigned data (#23) Anders Rundgren

Friday, 22 December 2017

Re: [w3c/payment-request] Billing address type (#664) ianbjacobs
Re: [w3c/payment-request] Merchant validation (#646) Rouslan Solomakhin

Thursday, 21 December 2017

Re: [w3c/payment-request] Merchant validation (#646) aestes
[w3c/payment-request] Billing address type (#664) jarrenwe26
Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Ade Bateman

Wednesday, 20 December 2017

Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) TSMatthews
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] PaymentAddress 'region' inconsistencies (#663) Rouslan Solomakhin
Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Marcos Cáceres
Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Sebsg
Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Rouslan Solomakhin
Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Marcos Cáceres
Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Rouslan Solomakhin
Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Sebsg
Re: [w3c/payment-request] Third-party payment handlers (#640) ianbjacobs
Re: [w3c/payment-request] Third-party payment handlers (#640) ianbjacobs
Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Marcos Cáceres
Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Rouslan Solomakhin
Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Rouslan Solomakhin
Re: [w3c/payment-request] Require user gesture when `.show()` is called (#651) Tantek Çelik
Re: [w3c/payment-request] Require user gesture when `.show()` is called (#651) Marcos Cáceres
Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Marcos Cáceres

Tuesday, 19 December 2017

Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) TSMatthews
Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) oconnortmaster
Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Marcos Cáceres

Monday, 18 December 2017

Re: [w3c/webpayments-methods-tokenization] Proposal for dealing with Signed and Unsigned data (#23) Anders Rundgren
Re: [w3c/webpayments-methods-tokenization] Proposal for dealing with Signed and Unsigned data (#23) Adrian Hope-Bailie
Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Rouslan Solomakhin
Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) ianbjacobs
Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) ianbjacobs
[w3c/payment-handler] add a "public computing" section to security/privacy considerations (#244) ianbjacobs
Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) Marcos Cáceres
Re: [w3c/payment-handler] Does payment instrument registration imply a display order? (#243) ianbjacobs
Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) ianbjacobs
Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Marcos Cáceres
Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Rouslan Solomakhin
Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) TSMatthews
Re: [w3c/payment-request] Merchant validation (#646) aestes

Sunday, 17 December 2017

Re: [w3c/payment-request] Merchant validation (#646) Rouslan Solomakhin
Re: [w3c/payment-request] Adding support for private-label credit cards (#662) Rouslan Solomakhin

Saturday, 16 December 2017

Re: [w3c/payment-handler] Recommended payment apps (#74) ianbjacobs
Re: [w3c/payment-handler] Recommended payment apps (#74) ianbjacobs
Re: [w3c/payment-request] Merchant validation (#646) aestes
Re: [w3c/payment-request] Merchant validation (#646) aestes
Re: [w3c/payment-request] Merchant validation (#646) aestes

Friday, 15 December 2017

Re: [w3c/payment-request] Adding support for private-label credit cards (#662) aestes
Re: [w3c/payment-handler] Recommended payment apps (#74) Rouslan Solomakhin
Re: [w3c/payment-request] Adding support for private-label credit cards (#662) Rouslan Solomakhin
Re: [w3c/payment-request] Adding support for private-label credit cards (#662) Rouslan Solomakhin
Re: [w3c/payment-request] Adding support for private-label credit cards (#662) Rouslan Solomakhin
Re: [w3c/payment-handler] Does payment instrument registration imply a display order? (#243) Adrian Hope-Bailie
Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Rouslan Solomakhin
Re: [w3c/payment-handler] Does payment instrument registration imply a display order? (#243) ianbjacobs
[w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) TSMatthews
Re: [w3c/payment-handler] Does payment instrument registration imply a display order? (#243) Adrian Hope-Bailie
Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) Adrian Hope-Bailie

Thursday, 14 December 2017

Wednesday, 13 December 2017

Tuesday, 12 December 2017

Monday, 11 December 2017

Sunday, 10 December 2017

Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) Marcos Cáceres

Saturday, 9 December 2017

Friday, 8 December 2017

Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) KJM
Re: [w3c/payment-request] ShippingAddressChange replaces address every time (#659) Domenic Denicola
Re: [w3c/payment-request] fine grained error recovery for fields (#647) Marcos Cáceres
Re: [w3c/payment-request] fine grained error recovery for fields (#647) Marcos Cáceres
Re: [w3c/payment-request] Is paypment request gated behind https? (#658) Rouslan Solomakhin
Re: [w3c/payment-request] fine grained error recovery for fields (#647) Rouslan Solomakhin
Re: [w3c/payment-request] ShippingAddressChange replaces address every time (#659) Adrian Hope-Bailie
Re: [w3c/payment-request] fine grained error recovery for fields (#647) Marcos Cáceres
Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Marcos Cáceres
[w3c/payment-request] ShippingAddressChange replaces address every time (#659) Marcos Cáceres
Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Marcos Cáceres
Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) Marcos Cáceres
Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) ianbjacobs
Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) ianbjacobs
Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) ianbjacobs
Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) Marcos Cáceres
Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) ianbjacobs
Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) ianbjacobs
Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) ianbjacobs
Re: [w3c/payment-handler] Make Origin and Instrument Display section non-normative. (#241) Marcos Cáceres
Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) Marcos Cáceres
Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Marcos Cáceres
Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Marcos Cáceres
Re: [w3c/payment-request] Is paypment request gated behind https? (#658) John-David Dalton
Re: [w3c/payment-request] Standardize phone number format (#652) Marcos Cáceres
Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Marcos Cáceres
Re: [w3c/payment-request] updateWith accepts a details object? (#657) Marcos Cáceres
Re: [w3c/payment-request] updateWith accepts a details object? (#657) Marcos Cáceres
Re: [w3c/payment-request] Is paypment request gated behind https? (#658) Marcos Cáceres
Re: [w3c/payment-request] Is paypment request gated behind https? (#658) Marcos Cáceres
Re: [w3c/payment-request] updateWith accepts a details object? (#657) Jinho Bang
Re: [w3c/payment-request] Is paypment request gated behind https? (#658) Jinho Bang
[w3c/payment-request] Is paypment request gated behind https? (#658) John-David Dalton
[w3c/payment-request] updateWith accepts a details object? (#657) John-David Dalton

Thursday, 7 December 2017

Re: [w3c/payment-handler] Remove 'Origin and Instrument Display for Selection' sections (#229) Marcos Cáceres
[w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) ianbjacobs
Re: [w3c/payment-handler] Make Origin and Instrument Display section non-normative. (#241) ianbjacobs
Re: [w3c/payment-handler] Make Origin and Instrument Display section non-normative. (#241) Manu Sporny
Re: [w3c/payment-handler] Make Origin and Instrument Display section non-normative. (#241) ianbjacobs
[w3c/payment-handler] Make Origin and Instrument Display section non-normative. (#241) Manu Sporny
Re: [w3c/payment-handler] Remove 'Origin and Instrument Display for Selection' sections (#229) ianbjacobs
Re: [w3c/payment-handler] Remove 'Origin and Instrument Display for Selection' sections (#229) KJM
Re: [w3c/payment-handler] Remove 'Origin and Instrument Display for Selection' sections (#229) Manu Sporny
Re: [w3c/payment-request] fine grained error recovery for fields (#647) Rouslan Solomakhin
Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Adrian Hope-Bailie
Re: [w3c/payment-handler] What happens when clearing site data? (#236) Adrian Hope-Bailie
Re: [w3c/payment-request] Should PaymentItems have a type? (#163) 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) Adrian Hope-Bailie
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/payment-handler] Share user data with Payment App (#123) Adrian Hope-Bailie
Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Adrian Hope-Bailie
Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Adrian Hope-Bailie
Re: [w3c/payment-handler] What happens when clearing site data? (#236) Adrian Hope-Bailie
Re: [w3c/payment-handler] What happens when clearing site data? (#236) Adrian Hope-Bailie
Re: [w3c/payment-handler] Remove 'Origin and Instrument Display for Selection' sections (#229) Adrian Hope-Bailie
Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Marcos Cáceres
Re: [w3c/payment-request] fine grained error recovery for fields (#647) Marcos Cáceres
Re: [w3c/payment-request] fine grained error recovery for fields (#647) Matt N.
Re: [w3c/payment-request] fine grained error recovery for fields (#647) Marcos Cáceres
Re: [w3c/payment-request] fine grained error recovery for fields (#647) Marcos Cáceres
Re: [w3c/payment-request] fine grained error recovery for fields (#647) Marcos Cáceres
Re: [w3c/payment-request] fine grained error recovery for fields (#647) Matt N.
Re: [w3c/payment-request] WIP: add constructor to PaymentAddress (#654) Marcos Cáceres
Re: [w3c/payment-request] fine grained error recovery for fields (#647) Marcos Cáceres

Wednesday, 6 December 2017

Re: [w3c/payment-request] WIP: add constructor to PaymentAddress (#654) Marcos Cáceres
Re: [w3c/payment-handler] Share user data with Payment App (#123) ianbjacobs
Re: [w3c/payment-handler] Share user data with Payment App (#123) Rouslan Solomakhin
Re: [w3c/payment-handler] Share user data with Payment App (#123) ianbjacobs
Re: [w3c/payment-handler] Share user data with Payment App (#123) Rouslan Solomakhin
Re: [w3c/payment-handler] Share user data with Payment App (#123) Krystian Czesak
Re: [w3c/payment-handler] Share user data with Payment App (#123) Rouslan Solomakhin
Re: [w3c/payment-handler] Share user data with Payment App (#123) Krystian Czesak
Re: [w3c/payment-handler] Allow Payment instrument to respond with user data (#218) Krystian Czesak
Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Rouslan Solomakhin
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
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] Should PaymentItems have a type? (#163) Marcos Cáceres
Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Marcos Cáceres
Re: [w3c/payment-handler] Remove 'Origin and Instrument Display for Selection' sections (#229) Marcos Cáceres
Re: [w3c/payment-handler] Remove 'Origin and Instrument Display for Selection' sections (#229) ianbjacobs

Tuesday, 5 December 2017

Re: [w3c/payment-handler] What happens when clearing site data? (#236) Dave Longley
Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Rouslan Solomakhin
Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Adrian Hope-Bailie
Re: [w3c/payment-handler] What happens when clearing site data? (#236) Jake Archibald
Re: [w3c/payment-handler] Remove 'Origin and Instrument Display for Selection' sections (#229) Marcos Cáceres

Monday, 4 December 2017

Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Matt N.
Re: [w3c/payment-handler] User consent and permissions (#239) Rouslan Solomakhin
Re: [w3c/payment-handler] User consent and permissions (#239) Dave Longley
Re: [w3c/payment-handler] What happens when clearing site data? (#236) Dave Longley
Re: [w3c/payment-handler] What happens when clearing site data? (#236) Dave Longley
Re: [w3c/payment-handler] User consent and permissions (#239) ianbjacobs
Re: [w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22) ianbjacobs
Re: [w3c/payment-handler] fix: PaymentInstruments.get not exceptional (#231) Marcos Cáceres
Re: [w3c/payment-handler] User consent and permissions (#239) Rouslan Solomakhin
Re: [w3c/payment-handler] User consent and permissions (#239) ianbjacobs
Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Rouslan Solomakhin
Re: [w3c/payment-handler] What happens when clearing site data? (#236) Adrian Hope-Bailie
Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Jinho Bang
Re: [w3c/payment-handler] fix: PaymentInstruments.get not exceptional (#231) Jinho Bang
Re: [w3c/payment-handler] What happens when clearing site data? (#236) Jinho Bang
Re: [w3c/payment-handler] fix: PaymentInstruments.get not exceptional (#231) Marcos Cáceres
Re: [w3c/payment-request] show() must be triggered by user activation (#655) Marcos Cáceres

Sunday, 3 December 2017

Re: [w3c/payment-handler] What happens when clearing site data? (#236) Marcos Cáceres
Re: [w3c/payment-handler] Add AbortPaymentEvent. (#207) Rouslan Solomakhin
Re: [w3c/payment-handler] Add AbortPaymentEvent. (#207) Rouslan Solomakhin
Re: [w3c/payment-handler] Editorial: trim introduction (#227) Marcos Cáceres
Re: [w3c/payment-method-id] Define syntax of standard PMI (closes #48) (c4bafc1) DonGlazik
Re: [w3c/payment-method-id] Define syntax of standard PMI (closes #48) (c4bafc1) DonGlazik
Re: [w3c/payment-handler] Editorial: trim/relocate conformance (#226) Marcos Cáceres

Friday, 1 December 2017

Re: [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-request] show() must be triggered by user activation (#655) Rouslan Solomakhin
Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Rouslan Solomakhin
Re: [w3c/payment-handler] Just-in-time payment handler install (#240) ianbjacobs
Re: [w3c/payment-handler] Editorial: trim/relocate conformance (#226) ianbjacobs
Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Adrian Hope-Bailie
Re: [w3c/payment-handler] User consent and permissions (#239) Adrian Hope-Bailie
Re: [w3c/payment-handler] Editorial: trim introduction (#227) ianbjacobs
Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Marcos Cáceres
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
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
Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Marcos Cáceres
Re: [w3c/payment-request] WIP: add constructor to PaymentAddress (#654) Domenic Denicola
Re: [w3c/payment-request] show() must be triggered by user activation (#655) Domenic Denicola

Last message date: Friday, 29 December 2017 13:10:13 UTC