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

Monday, 30 April 2018

• Re: [w3c/webpayments-methods-tokenization] Multiuse flow (#20) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Multiuse flow (#20) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Token properties? (#25) ianbjacobs
• [w3c/webpayments-methods-tokenization] Should encryption of tokenized card payment data be optional? (#39) ianbjacobs
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) Peter Saint-Andre
• Re: [w3c/payment-request] Verifying the total (#702) Peter Saint-Andre
• Re: [w3c/payment-handler] Suggest changing a shape of openWindow() (#300) ianbjacobs
• Re: [w3c/payment-request] editorial: better payment handler integration (#700) Domenic Denicola
• Re: [w3c/payment-method-basic-card] add: User changes payment method section (#53) Domenic Denicola
• Re: [w3c/payment-handler] Suggest changing a shape of openWindow() (#300) gogerald
• Re: [w3c/payment-request] WIP: add paymentmethodchanged event (#695) Domenic Denicola
• Re: [w3c/payment-request] WIP: add paymentmethodchanged event (#695) Domenic Denicola
• [w3c/payment-handler] Suggest changing a shape of openWindow() (#300) Jinho Bang
• Re: [w3c/payment-method-basic-card] add: User changes payment method section (#53) ianbjacobs
• Re: [w3c/payment-request] Add regionCode attribute (#690) Marcos Cáceres
• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Marcos Cáceres
• Re: [w3c/payment-request] WIP: add paymentmethodchanged event (#695) Marcos Cáceres
• Re: [w3c/payment-request] WIP: add paymentmethodchanged event (#695) Marcos Cáceres
• [w3c/payment-method-basic-card] add: User changes payment method section (#53) Marcos Cáceres
• Re: [w3c/payment-request] WIP: add paymentmethodchanged event (#695) Marcos Cáceres
• Re: [w3c/payment-request] editorial: better payment handler integration (#700) Marcos Cáceres
• Re: [w3c/payment-request] editorial: better payment handler integration (#700) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] better integration with PR API (#52) Marcos Cáceres
• Re: [w3c/payment-request] editorial: better payment handler integration (#700) Marcos Cáceres

Saturday, 28 April 2018

• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) Jun

Friday, 27 April 2018

• Re: [w3c/payment-request] A distinct invoice address should be supported (#550) Marcos Cáceres

Thursday, 26 April 2018

• Re: [w3c/payment-request] A distinct invoice address should be supported (#550) ianbjacobs
• Re: [w3c/payment-request] Add support for merchant validation (#646) Marcos Cáceres
• Re: [w3c/payment-request] Merchant-specified default shipping address (#653) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) ianbjacobs
• Re: [w3c/payment-method-basic-card] Brand selection (#49) ianbjacobs
• Re: [w3c/payment-handler] ImageObjects can now reference ImageResource (#238) ianbjacobs
• Re: [w3c/payment-handler] Need to reuse web app manifest ImageResource better. (#287) ianbjacobs
• Re: [w3c/payment-handler] Need to reuse web app manifest ImageResource better. (#287) ianbjacobs
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Peter Saint-Andre
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) ianbjacobs
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) ianbjacobs
• Re: [w3c/payment-request] Merchant-specified default shipping address (#653) Matt N.
• Re: [w3c/payment-request] Alternative 'Pay' button wording options for Browser UI (#701) Adrian Hope-Bailie
• Re: [w3c/payment-request] support of VAT (#699) Marcos Cáceres
• Re: [w3c/payment-request] Merchant-specified default shipping address (#653) Marcos Cáceres

Wednesday, 25 April 2018

• Re: [w3c/3ds] Communicating 3DS data in HTTP/JSON terms (#5) ianbjacobs
• Re: [w3c/payment-request] remove currencySystem member (#694) Marcos Cáceres
• Re: [w3c/payment-request] remove currencySystem member (#694) Marcos Cáceres
• Re: [w3c/payment-request] Verifying the total (#702) Marcos Cáceres

Tuesday, 24 April 2018

• Re: [w3c/payment-request] Verifying the total (#702) Peter Saint-Andre
• Re: [w3c/payment-request] remove currencySystem member (#694) Marcos Cáceres
• Re: [w3c/payment-request] Verifying the total (#702) Marcos Cáceres
• [w3c/payment-request] Verifying the total (#702) Peter Saint-Andre
• Re: [w3c/payment-request] remove currencySystem member (#694) ianbjacobs
• [w3c/3ds] Communicating 3DS data in HTTP/JSON terms (#5) ianbjacobs
• Re: [w3c/payment-handler] Normative what happens when users closing the window opened by PaymentRequestEvent.openWindow (#299) gogerald
• [w3c/payment-handler] Normative what happens when users closing the window opened by PaymentRequestEvent.openWindow (#299) gogerald
• Re: [w3c/payment-request] remove currencySystem member (#694) Marcos Cáceres
• Re: [w3c/payment-request] remove currencySystem member (#694) ianbjacobs

Monday, 23 April 2018

• Re: [w3c/payment-handler] Consider explaining the connection with payment method manifests sooner (#269) ianbjacobs
• Re: [w3c/payment-handler] Define the feature policy for the Payment Handler content (#298) Marcos Cáceres
• Re: [w3c/payment-handler] Consider explaining the connection with payment method manifests sooner (#269) Marcos Cáceres
• Re: [w3c/payment-request] chore: rename repo to match shortname (149c391) Marcos Cáceres
• Re: [w3c/payment-request] chore: rename repo to match shortname (149c391) Bailey520

Sunday, 22 April 2018

• Re: [w3c/payment-request] chore: rename repo to match shortname (149c391) Marcos Cáceres
• Re: [w3c/payment-request] chore: rename repo to match shortname (149c391) Bailey520

Friday, 20 April 2018

• Re: [w3c/payment-handler] Consider explaining the connection with payment method manifests sooner (#269) Anthony Vallee-Dubois
• [w3c/payment-handler] Define the feature policy for the Payment Handler content (#298) Anthony Vallee-Dubois
• Re: [w3c/payment-handler] topLevelOrigin is a weird name (#259) Anthony Vallee-Dubois

Thursday, 19 April 2018

• Re: [w3c/payment-request] A distinct invoice address should be supported (#550) Matt N.
• Re: [w3c/payment-request] A distinct invoice address should be supported (#550) mattsaxon
• Re: [w3c/payment-request] retry and fine grained error recovery for fields (#647) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) Peter Saint-Andre
• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Marcos Cáceres
• Re: [w3c/payment-request] Alternative 'Pay' button wording options for Browser UI (#701) Hexalys

Wednesday, 18 April 2018

• Re: [w3c/webpayments-methods-tokenization] Relationship between TokenizedCard and EncryptedTokenizedCard needs clarification (#35) Adrian Hope-Bailie
• Re: [w3c/payment-method-basic-card] Brand selection (#49) mattsaxon
• Re: [w3c/payment-method-basic-card] Brand selection (#49) mattsaxon
• Re: [w3c/payment-handler] Popup messages (#297) ianbjacobs

Tuesday, 17 April 2018

• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) Matt N.
• Re: [w3c/payment-handler] Popup messages (#297) majaybabu
• Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) Marcos Cáceres
• Re: [w3c/payment-handler] Remove link to issue 157 (#292) Marcos Cáceres
• Re: [w3c/payment-handler] Add [SameObject] to paymentManager attribute (#293) Jinho Bang
• Re: [w3c/payment-handler] Throws NotAllowedError instead of InvalidAccessError (#291) Jinho Bang
• Re: [w3c/payment-handler] Popup messages (#297) Jinho Bang
• Re: [w3c/payment-handler] Popup messages (#297) majaybabu

Monday, 16 April 2018

• Re: [w3c/payment-handler] Open Window Algorithm (#115) Dave Longley
• [w3c/payment-handler] Popup messages (#297) majaybabu
• Re: [w3c/payment-handler] Need to specify CanMakePaymentEvent.respondWith() behavior (#295) Peter Saint-Andre
• Re: [w3c/payment-handler] Open Window Algorithm (#115) Jinho Bang
• Re: [w3c/payment-handler] Should throw InvalidStateError if PaymentRequestEvent is not trusted (#294) Rouslan Solomakhin (OOO until July 17)
• Re: [w3c/payment-handler] Define CanMakePaymentEvent.respondWith() behavior (#296) Jinho Bang
• Re: [w3c/payment-handler] Define CanMakePaymentEvent.respondWith() behavior (#296) Rouslan Solomakhin (OOO until July 17)
• Re: [w3c/payment-handler] Define CanMakePaymentEvent.respondWith() behavior (#296) Rouslan Solomakhin (OOO until July 17)
• [w3c/payment-handler] Define CanMakePaymentEvent.respondWith() behavior (#296) Jinho Bang
• [w3c/payment-handler] Need to specify CanMakePaymentEvent.respondWith() behavior (#295) Jinho Bang
• Re: [w3c/payment-handler] Throws NotAllowedError instead of InvalidAccessError (#291) Rouslan Solomakhin (OOO until July 17)
• Re: [w3c/webpayments-methods-tokenization] Add PAR to response data? (#38) ianbjacobs
• Re: [w3c/payment-handler] Throws NotAllowedError instead of InvalidAccessError (#291) Jinho Bang
• Re: [w3c/payment-handler] Add [SameObject] to paymentManager attribute (#293) Rouslan Solomakhin
• Re: [w3c/payment-handler] Throws NotAllowedError instead of InvalidAccessError (#291) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add [SameObject] to paymentManager attribute (#293) Jinho Bang
• Re: [w3c/payment-handler] Throws NotAllowedError instead of InvalidAccessError (#291) Jinho Bang
• Re: [w3c/payment-handler] Should throw InvalidStateError if PaymentRequestEvent is not trusted (#294) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add [SameObject] to paymentManager attribute (#293) Rouslan Solomakhin
• Re: [w3c/payment-handler] Should throw InvalidStateError if PaymentRequestEvent is not trusted (#294) Jinho Bang
• Re: [w3c/payment-handler] Add [SecureContext, SameObject] to paymentManager attribute (#293) Jinho Bang
• Re: [w3c/payment-handler] Should throw InvalidStateError if PaymentRequestEvent is not trusted (#294) Rouslan Solomakhin
• Re: [w3c/payment-handler] Should throw InvalidStateError if PaymentRequestEvent is not trusted (#294) Jinho Bang
• Re: [w3c/payment-handler] Throws SecurityError instead of InvalidAccessError (#291) Rouslan Solomakhin
• Re: [w3c/payment-handler] Remove link to issue 157 (#292) Rouslan Solomakhin
• Re: [w3c/payment-handler] Remove link to issue 157 (#292) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add [SecureContext, SameObject] to paymentManager attribute (#293) Rouslan Solomakhin
• Re: [w3c/payment-handler] Should throw InvalidStateError if PaymentRequestEvent is not trusted (#294) Rouslan Solomakhin
• Re: [w3c/payment-request] updateWith(data) should merge with request.data (#649) Rouslan Solomakhin
• Re: [w3c/payment-request] updateWith(data) should merge with request.data (#649) Marcos Cáceres
• Re: [w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249) Marcos Cáceres
• Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) Marcos Cáceres

Sunday, 15 April 2018

• [w3c/payment-handler] Should throw InvalidStateError if PaymentRequestEvent is not trusted (#294) Jinho Bang
• [w3c/payment-handler] Add [SecureContext, SameObject] to paymentManager attribute (#293) Jinho Bang
• [w3c/payment-handler] Remove link to issue 157 (#292) Jinho Bang
• [w3c/payment-handler] Throws SecurityError instead of InvalidAccessError (#291) Jinho Bang

Saturday, 14 April 2018

• Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) BartłomiejG.

Friday, 13 April 2018

• Re: [w3c/3ds] Value proposition (#4) Jimbray4
• Re: [w3c/payment-handler] HEAD request for supportedMethods not getting triggered (#286) ianbjacobs
• Re: [w3c/payment-handler] HEAD request for supportedMethods not getting triggered (#286) ianbjacobs
• Re: [w3c/payment-request] Alternative 'Pay' button wording options for Browser UI (#701) Peter Saint-Andre
• Re: [w3c/payment-request] Alternative 'Pay' button wording options for Browser UI (#701) Hexalys
• Re: [w3c/payment-request] Alternative 'Pay' button wording options for Browser UI (#701) Marcos Cáceres
• Re: [w3c/payment-request] Alternative 'Pay' button wording options for Browser UI (#701) Marcos Cáceres
• Re: [w3c/payment-request] Alternative 'Pay' button wording options for Browser UI (#701) Hexalys

Thursday, 12 April 2018

• Re: [w3c/payment-request] PaymentRequest does not handle the case of store pickup (#389) Bailey520
• Re: [w3c/payment-handler] ImageObjects can now reference ImageResource (#238) Domenic Denicola
• Re: [w3c/payment-handler] ImageObjects can now reference ImageResource (#238) Kenneth Rohde Christiansen
• Re: [w3c/payment-handler] Need to reuse web app manifest ImageResource better. (#287) Kenneth Rohde Christiansen
• Re: [w3c/payment-handler] ImageObjects can now reference ImageResource (#238) Domenic Denicola
• Re: [w3c/payment-handler] ImageObjects can now reference ImageResource (#238) Kenneth Rohde Christiansen
• Re: [w3c/payment-handler] Call out the need for merchants to validate payment responses (#288) Peter Saint-Andre
• Re: [w3c/payment-handler] HEAD request for supportedMethods not getting triggered (#286) majaybabu
• Re: [w3c/payment-handler] Open Window Algorithm (#115) ianbjacobs
• Re: [w3c/payment-handler] ImageObjects can now reference ImageResource (#238) Rouslan Solomakhin
• Re: [w3c/payment-handler] Need to reuse web app manifest ImageResource better. (#287) Rouslan Solomakhin
• Re: [w3c/payment-handler] Need to reuse web app manifest ImageResource better. (#287) Domenic Denicola
• [w3c/payment-handler] Update Example6 and Example7 (#290) Jinho Bang
• Re: [w3c/payment-handler] Remove modifiers from CanMakePaymentEvent? (#289) Rouslan Solomakhin
• Re: [w3c/payment-handler] Remove modifiers from CanMakePaymentEvent? (#289) ianbjacobs
• Re: [w3c/payment-handler] HEAD request for supportedMethods not getting triggered (#286) Rouslan Solomakhin
• Re: [w3c/payment-handler] Call out the need for merchants to validate payment responses (#288) Rouslan Solomakhin
• Re: [w3c/payment-handler] HEAD request for supportedMethods not getting triggered (#286) majaybabu
• [w3c/payment-handler] Remove modifiers from CanMakePaymentEvent? (#289) Rouslan Solomakhin
• Re: [w3c/payment-handler] Call out the need for merchants to validate payment responses (#288) Peter Saint-Andre
• [w3c/payment-handler] Call out the need for merchants to validate payment responses (#288) Rouslan Solomakhin
• [w3c/payment-handler] Need to reuse web app manifest ImageResource better. (#287) Rouslan Solomakhin

Wednesday, 11 April 2018

• Re: [w3c/payment-handler] HEAD request for supportedMethods not getting triggered (#286) majaybabu
• Re: [w3c/payment-handler] HEAD request for supportedMethods not getting triggered (#286) majaybabu
• Re: [w3c/payment-handler] HEAD request for supportedMethods not getting triggered (#286) Rouslan Solomakhin
• Re: [w3c/payment-handler] HEAD request for supportedMethods not getting triggered (#286) majaybabu
• Re: [w3c/payment-handler] HEAD request for supportedMethods not getting triggered (#286) Rouslan Solomakhin
• [w3c/payment-handler] HEAD request for supportedMethods not getting triggered (#286) kishoretulsiani
• Re: [w3c/payment-handler] Open Window Algorithm (#115) Rouslan Solomakhin
• Re: [w3c/payment-handler] Establish Editorial process (#156) ianbjacobs
• Re: [w3c/payment-handler] Establish Editorial process (#156) ianbjacobs
• Re: [w3c/payment-handler] Open Window Algorithm (#115) ianbjacobs
• Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157) ianbjacobs
• Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157) ianbjacobs
• Re: [w3c/payment-handler] Should PaymentInstruments.set() be immutable? (#285) Alexander Shalamov
• Re: [w3c/payment-handler] Should PaymentInstruments.set() be immutable? (#285) Jinho Bang
• [w3c/payment-handler] Should PaymentInstruments.set() be immutable? (#285) Alexander Shalamov

Tuesday, 10 April 2018

• Re: [w3c/payment-request] Alternative 'Pay' button wording options for Browser UI (#701) Marcos Cáceres
• Re: [w3c/payment-request] Alternative 'Pay' button wording options for Browser UI (#701) ianbjacobs

Monday, 9 April 2018

• Re: [w3c/payment-handler] topLevelOrigin is a weird name (#259) Adrian Hope-Bailie
• Re: [w3c/payment-request] Alternative 'Pay' button wording options for Browser UI (#701) Adrian Hope-Bailie
• Re: [w3c/3ds] Value proposition (#4) ianbjacobs
• Re: [w3c/payment-handler] topLevelOrigin is a weird name (#259) Adrian Hope-Bailie
• Re: [w3c/payment-handler] HTTPS considerations. (#283) ianbjacobs
• Re: [w3c/payment-handler] HTTPS considerations. (#283) ianbjacobs
• Re: [w3c/payment-handler] Found some typos in the wiki (#284) Mattijs Bliek
• Re: [w3c/payment-handler] Found some typos in the wiki (#284) Mattijs Bliek
• Re: [w3c/payment-request] remove currencySystem member (#694) Adrian Hope-Bailie
• Re: [w3c/payment-handler] Found some typos in the wiki (#284) ianbjacobs
• [w3c/payment-handler] Found some typos in the wiki (#284) Mattijs Bliek
• [w3c/payment-handler] HTTPS considerations. (#283) Rouslan Solomakhin
• [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) Rouslan Solomakhin
• Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) Rouslan Solomakhin
• Re: [w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249) Rouslan Solomakhin
• Re: [w3c/payment-handler] window.open not working from paymentrequest eventlistener (#280) Rouslan Solomakhin

Saturday, 7 April 2018

• Re: [w3c/payment-request] Add support for merchant validation (#646) Rouslan Solomakhin
• [w3c/payment-request] Alternative Options for 'Pay' button provided in the Browser UI (#701) Hexalys
• Re: [w3c/payment-request] Add support for merchant validation (#646) Kane York

Friday, 6 April 2018

• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) Kane York
• Re: [w3c/payment-handler] topLevelOrigin is a weird name (#259) Rouslan Solomakhin
• Re: [w3c/payment-handler] topLevelOrigin is a weird name (#259) Domenic Denicola
• Re: [w3c/payment-handler] topLevelOrigin is a weird name (#259) Rouslan Solomakhin
• Re: [w3c/payment-handler] topLevelOrigin is a weird name (#259) Domenic Denicola
• Re: [w3c/payment-handler] topLevelOrigin is a weird name (#259) Rouslan Solomakhin
• Re: [w3c/payment-request] Add regionCode attribute (#690) Domenic Denicola
• Re: [w3c/payment-handler] topLevelOrigin is a weird name (#259) Domenic Denicola
• Re: [w3c/payment-request] editorial: better payment handler integration (#700) ianbjacobs
• Re: [w3c/payment-request] editorial: better payment handler integration (#700) ianbjacobs
• Re: [w3c/payment-request] remove currencySystem member (#694) ianbjacobs
• Re: [w3c/payment-request] remove currencySystem member (#694) ianbjacobs
• Re: [w3c/payment-request] editorial: better payment handler integration (#700) Marcos Cáceres
• Re: [w3c/payment-request] editorial: better payment handler integration (#700) Marcos Cáceres
• [w3c/payment-request] editorial: better payment handler integration (#700) Marcos Cáceres
• Re: [w3c/payment-request] canMakePayment() needs to match .show() (#535) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: align show() and canMakePayment() #535 (#682) Marcos Cáceres
• Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) Marcos Cáceres
• Re: [w3c/payment-request] remove currencySystem member (#694) Marcos Cáceres

Thursday, 5 April 2018

• Re: [w3c/payment-handler] Block payment handler in iframes by default (#281) ianbjacobs
• Re: [w3c/payment-handler] Block payment handler in iframes by default (#281) Rouslan Solomakhin
• Re: [w3c/payment-handler] Block payment handler in iframes by default (#281) ianbjacobs
• Re: [w3c/payment-handler] window.open not working from paymentrequest eventlistener (#280) majaybabu
• Re: [w3c/payment-method-basic-card] WIP - better integration with PR API (#52) Rouslan Solomakhin
• [w3c/payment-handler] Block payment handler in iframes by default (#281) Rouslan Solomakhin
• Re: [w3c/payment-request] remove currencySystem member (#694) ianbjacobs
• Re: [w3c/payment-method-basic-card] Connecting to payment request. (#50) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Connecting to payment request. (#50) Marcos Cáceres
• [w3c/payment-method-basic-card] WIP - better integration with PR API (#52) Marcos Cáceres
• Re: [w3c/payment-request] remove currencySystem member (#694) Adrian Hope-Bailie
• Re: [w3c/payment-request] remove currencySystem member (#694) Marcos Cáceres
• Re: [w3c/payment-request] remove currencySystem member (#694) Marcos Cáceres
• Re: [w3c/payment-handler] window.open not working from paymentrequest eventlistener (#280) Jinho Bang
• Re: [w3c/payment-handler] window.open not working from paymentrequest eventlistener (#280) Rouslan Solomakhin
• Re: [w3c/payment-handler] window.open not working from paymentrequest eventlistener (#280) majaybabu
• Re: [w3c/payment-handler] window.open not working from paymentrequest eventlistener (#280) majaybabu

Wednesday, 4 April 2018

• Re: [w3c/payment-handler] window.open not working from paymentrequest eventlistener (#280) Jinho Bang
• Re: [w3c/payment-handler] window.open not working from paymentrequest eventlistener (#280) majaybabu
• Re: [w3c/webpayments-methods-tokenization] Add PAR to response data? (#38) ianbjacobs
• Re: [w3c/payment-request] remove currencySystem member (#694) ianbjacobs
• Re: [w3c/payment-handler] window.open not working from paymentrequest eventlistener (#280) Jinho Bang
• Re: [w3c/payment-handler] window.open not working from paymentrequest eventlistener (#280) majaybabu
• Re: [w3c/payment-handler] window.open not working from paymentrequest eventlistener (#280) Rouslan Solomakhin
• Re: [w3c/payment-handler] window.open not working from paymentrequest eventlistener (#280) majaybabu
• Re: [w3c/payment-request] Add regionCode attribute (#690) Marcos Cáceres
• Re: [w3c/payment-request] Add regionCode attribute (#690) Matt N.
• Re: [w3c/payment-method-basic-card] Connecting to payment request. (#50) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Connecting to payment request. (#50) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Connecting to payment request. (#50) Marcos Cáceres
• Re: [w3c/payment-request] WIP: add paymentmethodchanged event (#695) Marcos Cáceres
• Re: [w3c/payment-request] Add regionCode attribute (#690) Marcos Cáceres
• Re: [w3c/payment-request] remove currencySystem member (#694) Marcos Cáceres
• Re: [w3c/payment-handler] window.open not working from paymentrequest eventlistener (#280) Rouslan Solomakhin
• Re: [w3c/payment-handler] window.open not working from paymentrequest eventlistener (#280) Jinho Bang
• [w3c/payment-handler] window.open not working from paymentrequest eventlistener (#280) majaybabu

Tuesday, 3 April 2018

• Re: [w3c/payment-handler] Origin definitions are imprecise (#263) Domenic Denicola
• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) Ian Clelland
• Re: [w3c/payment-method-basic-card] Connecting to payment request. (#50) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Connecting to payment request. (#50) Rouslan Solomakhin
• [w3c/webpayments-methods-tokenization] Add PAR to response data? (#38) ianbjacobs
• Re: [w3c/payment-method-basic-card] Connecting to payment request. (#50) ianbjacobs
• Re: [w3c/payment-method-basic-card] Connecting to payment request. (#50) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) Rouslan Solomakhin
• Re: [w3c/payment-handler] Consistent use of quotes. (#278) Rouslan Solomakhin
• Re: [w3c/payment-handler] Consistent use of quotes. (#278) Rouslan Solomakhin
• Re: [w3c/payment-handler] Link ot issue 115 that supersedes issue 97 (#279) ianbjacobs
• Re: [w3c/payment-handler] Link ot issue 115 that supersedes issue 97 (#279) Rouslan Solomakhin
• Re: [w3c/payment-handler] Link ot issue 115 that supersedes issue 97 (#279) Rouslan Solomakhin
• Re: [w3c/payment-handler] Remove link to issue 97, because it is now closed. (#279) Rouslan Solomakhin
• Re: [w3c/payment-handler] Remove link to issue 97, because it is now closed. (#279) ianbjacobs
• Re: [w3c/payment-handler] Consistent use of quotes. (#278) ianbjacobs
• [w3c/payment-handler] Remove link to issue 97, because it is now closed. (#279) Rouslan Solomakhin
• Re: [w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276) Rouslan Solomakhin
• Re: [w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276) Rouslan Solomakhin
• Re: [w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276) Rouslan Solomakhin
• Re: [w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276) Rouslan Solomakhin
• Re: [w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276) Rouslan Solomakhin
• Re: [w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276) Rouslan Solomakhin
• [w3c/payment-handler] Consistent use of quotes. (#278) Rouslan Solomakhin
• Re: [w3c/payment-request] remove currencySystem member (#694) ianbjacobs
• Re: [w3c/payment-request] remove currencySystem member (#694) Marcos Cáceres

Monday, 2 April 2018

• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) Domenic Denicola
• Re: [w3c/webpayments-methods-tokenization] Inconsistencies in response example (#37) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Inconsistencies in response example (#37) ianbjacobs
• Re: [w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276) ianbjacobs
• Re: [w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276) ianbjacobs
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) ianbjacobs
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) ianbjacobs
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) ianbjacobs
• Re: [w3c/payment-request] A distinct invoice address should be supported (#550) GSPP
• Re: [w3c/3ds] Value proposition (#4) KJM

Last message date: Monday, 30 April 2018 22:54:23 UTC