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

Thursday, 31 August 2017

• Re: [w3c/payment-request] Throw on dup shippingOptions ids (#596) Zach Koch
• Re: [w3c/payment-method-id] Define syntax of standard PMI (closes #48) (#49) Marcos Cáceres
• Re: [w3c/payment-method-id] Better defined validity of standardized PMIs? (#48) Marcos Cáceres
• Re: [w3c/payment-method-id] Define syntax of standard PMI (closes #48) (#49) Marcos Cáceres
• Re: [w3c/payment-method-id] Define syntax of standard PMI (closes #48) (#49) Zach Koch
• Re: [w3c/payment-method-id] Define syntax of standard PMI (closes #48) (#49) Ade Bateman
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Ade Bateman
• Re: [w3c/payment-request] Empty shippingOptions (ab)used as error (#595) Ade Bateman
• Re: [w3c/payment-request] Empty shippingOptions (ab)used as error (#595) Ade Bateman
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, #595) (#596) Marcos Cáceres
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, #595) (#596) Ade Bateman
• Re: [w3c/payment-request] l10n: adds Localizable dict + TextDirection enum (#455) Marcos Cáceres
• Re: [w3c/payment-request] l10n: adds Localizable dict + TextDirection enum (#455) Marcos Cáceres
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, #595) (#596) Marcos Cáceres
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, #595) (#596) Marcos Cáceres
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, #595) (#596) Marcos Cáceres
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Marcos Cáceres
• Re: [w3c/payment-request] Behavior for multiple modifiers for the same payment method is not defined (#309) Marcos Cáceres
• Re: [w3c/payment-request] validate supportedMethods (#464) Marcos Cáceres
• Re: [w3c/payment-method-id] Other specs must define validity rules (closes #46) (#47) Marcos Cáceres
• Re: [w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Domenic Denicola

Wednesday, 30 August 2017

• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) ianbjacobs
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) ianbjacobs
• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) Jinho Bang
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Jinho Bang
• Re: [w3c/payment-handler] Add AbortPaymentEvent. (#207) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) ianbjacobs
• Re: [w3c/payment-handler] Add AbortPaymentEvent. (#207) Jinho Bang
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) Jinho Bang
• Re: [w3c/payment-method-id] Better defined validity of standardized PMIs? (#48) Marcos Cáceres
• Re: [w3c/payment-method-id] Better defined validity of standardized PMIs? (#48) Rouslan Solomakhin
• Re: [w3c/payment-handler] move dependency section down, as is done in PR API (#211) ianbjacobs
• Re: [w3c/payment-handler] Add link to payment handler test suite (#210) ianbjacobs
• Re: [w3c/payment-handler] Add AbortPaymentEvent. (#207) Marcos Cáceres
• Re: [w3c/payment-handler] Add link to payment handler test suite (#210) Marcos Cáceres
• Re: [w3c/payment-handler] move dependency section down, as is done in PR API (#211) Marcos Cáceres
• Re: [w3c/payment-handler] Establish Editorial process (#156) Marcos Cáceres
• [w3c/payment-method-id] Define syntax of standard PMI (closes #48) (#49) Marcos Cáceres
• [w3c/payment-method-id] Better define validity of standardized PMIs? (#48) Marcos Cáceres

Tuesday, 29 August 2017

• Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157) ianbjacobs
• Re: [w3c/payment-handler] Support for Abort() being delegated to Payment Handler (#117) ianbjacobs
• [w3c/payment-handler] move dependency section down, as is done in PR API (#211) ianbjacobs
• [w3c/payment-handler] Add link to payment handler test suite (#210) ianbjacobs
• Re: [w3c/payment-handler] Make explicit which origin to use in conjunction with payment method manifest. (#209) ianbjacobs
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) ianbjacobs
• Re: [w3c/payment-handler] Add AbortPaymentEvent. (#207) Rouslan Solomakhin
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, #595) (#596) Marcos Cáceres
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, #595) (#596) Marcos Cáceres

Monday, 28 August 2017

• [w3c/payment-handler] Make explicit which origin to use in conjunction with payment method manifest. (#209) Rouslan Solomakhin
• Re: [w3c/payment-handler] Clarify empty instrument key meaning. (#208) ianbjacobs
• Re: [w3c/payment-handler] Clarify empty instrument key meaning. (#208) Rouslan Solomakhin
• Re: [w3c/payment-handler] Clarify empty instrument key meaning. (#208) ianbjacobs
• [w3c/payment-handler] Clarify empty instrument key meaning. (#208) Rouslan Solomakhin
• [w3c/payment-handler] Add AbortPaymentEvent. (#207) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Marcos Cáceres
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Marcos Cáceres
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Dave Longley
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres

Saturday, 26 August 2017

• Re: [w3c/payment-request] https://www.w3.org/TR/payment-request/#conditional-modifications-to-payment-request (#597) Marcos Cáceres
• Re: [w3c/payment-request] https://www.w3.org/TR/payment-request/#conditional-modifications-to-payment-request (#597) Marcos Cáceres
• [w3c/payment-request] https://www.w3.org/TR/payment-request/#conditional-modifications-to-payment-request (#597) sabrinatseng
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres

Friday, 25 August 2017

• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Zach Koch
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Domenic Denicola
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Dave Longley
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Dave Longley
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) ianbjacobs
• Re: [w3c/payment-handler] tweak about usage (93e90af) Dave Longley
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) ianbjacobs
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Dave Longley
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Dave Longley
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Dave Longley
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Dave Longley
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Dave Longley
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Dave Longley
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Dave Longley
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Dave Longley
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) ianbjacobs
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) ianbjacobs
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Dave Longley
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Dave Longley
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Dave Longley
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) Rouslan Solomakhin
• [w3c/payment-handler] Add userHint to PaymentManager (#206) ianbjacobs
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, ##595) (#596) ianbjacobs
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, ##595) (#596) Marcos Cáceres
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, ##595) (#596) Marcos Cáceres
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, ##595) (#596) Marcos Cáceres
• Re: [w3c/payment-request] Throw on dup shippingOptions (closes #594, ##595) (#596) Marcos Cáceres
• [w3c/payment-request] Throw on dup shippingOptions (closes #594, ##595) (#596) Marcos Cáceres
• Re: [w3c/payment-request] Duplicate shippingOptions lead to inconsistent `updateWith()` - should throw! (#594) Marcos Cáceres
• Re: [w3c/payment-request] Empty shippingOptions (ab)used as error (#595) Marcos Cáceres
• Re: [w3c/payment-request] Empty shippingOptions (ab)used as error (#595) Marcos Cáceres
• [w3c/payment-request] Empty shippingOptions (ab)used as error (#595) Marcos Cáceres
• [w3c/payment-request] Duplicate shippingOptions lead to inconsistent `updateWith()` - should throw! (#594) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Domenic Denicola
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres

Thursday, 24 August 2017

• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Domenic Denicola
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Domenic Denicola
• Re: [w3c/payment-request] Third party Method not recognized- why (#593) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Relationship to PaymentRequest (#40) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Relationship to PaymentRequest (#40) Philip Jägenstedt
• Re: [w3c/payment-request] Third party Method not recognized- why (#593) Anders Rundgren
• Re: [w3c/payment-request] Third party Method not recognized- why (#593) Marcos Cáceres
• Re: [w3c/payment-request] Third party Method not recognized- why (#593) Marcos Cáceres
• [w3c/payment-request] Third party Method not recognized- why (#593) biseraivanovska
• Re: [w3c/payment-method-id] Other specs must define validity rules (closes #46) (#47) Marcos Cáceres
• [w3c/payment-method-id] Other specs must define validity rules (closes #46) (#47) Marcos Cáceres

Wednesday, 23 August 2017

• Re: [w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46) Moe Ahmadi
• Re: [w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46) Marcos Cáceres
• Re: [w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46) Moe Ahmadi
• Re: [w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46) Rouslan Solomakhin
• Re: [w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46) Marcos Cáceres
• Re: [w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46) Marcos Cáceres
• [w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46) Moe Ahmadi
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) Adrian Hope-Bailie
• Re: [w3c/payment-handler] Stop committing things without tests (#205) Adrian Hope-Bailie
• Re: [w3c/payment-handler] Stop committing things without tests (#205) Adrian Hope-Bailie
• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) Marcos Cáceres
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) Marcos Cáceres
• [w3c/payment-handler] Stop committing things without tests (#205) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• [w3c/payment-request] Consider adding some means of getting the details out of a payment request (#592) Marcos Cáceres

Tuesday, 22 August 2017

• Re: [w3c/webpayments-methods-tokenization] tokenProviderMerchantIdentifier vs merchantId (#18) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] tokenProviderMerchantIdentifier vs merchantId (#18) ianbjacobs
• Re: [w3c/payment-handler] Default handler icon? (#178) ianbjacobs
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) ianbjacobs
• Re: [w3c/payment-handler] Registration example accesses `registration` before it is defined (#200) ianbjacobs
• Re: [w3c/payment-handler] Simplify Payment Handler Registration example. (#204) ianbjacobs
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Don't block UI if .updateWith() not called (closes #589) (#590) Marcos Cáceres
• Re: [w3c/payment-request] Don't block UI if .updateWith() not called (closes #589) (#590) Marcos Cáceres
• Re: [w3c/payment-request] Don't block UI if .updateWith() not called (closes #589) (#590) Marcos Cáceres
• [w3c/payment-request] Don't block UI if .updateWith() not called (closes #589) (#590) Marcos Cáceres
• Re: [w3c/payment-request] .updateWith() should only be callable if event was canceled (#589) Marcos Cáceres
• [w3c/payment-request] .updateWith() should only be callable if event was cancelled (#589) Marcos Cáceres
• Re: [w3c/payment-handler] Simplify Payment Handler Registration example. (#204) Jinho Bang

Monday, 21 August 2017

• Re: [w3c/payment-request] Real use case for .complete("unknown") - or mark "at risk" (#584) Marcos Cáceres
• Re: [w3c/payment-request] Real use case for .complete("unknown") - or mark "at risk" (#584) Zach Koch
• [w3c/payment-handler] Simplify Payment Handler Registration example. (#204) Dave Longley
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-handler] The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense (#192) Rouslan Solomakhin
• Re: [w3c/payment-handler] The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense (#192) Rouslan Solomakhin
• Re: [w3c/payment-handler] Registration example accesses `registration` before it is defined (#200) ianbjacobs
• [w3c/payment-handler] Make explicit which origin to use in conjunction with payment method manifest (#203) ianbjacobs
• Re: [w3c/payment-handler] Add "Validate Methods Algorithm" (#197) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add "Validate Methods Algorithm" (#197) Rouslan Solomakhin
• Re: [w3c/webpayments-methods-tokenization] Wording of tokens used (#5) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Wording of tokens used (#5) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Structuring the tokenization payment method(s) (#13) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Structuring the tokenization payment method(s) (#13) ianbjacobs
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Adrian Hope-Bailie
• Re: [w3c/payment-request] After CR, evaluate if paymentRequest.id being a UUID is a must (#588) Marcos Cáceres
• [w3c/payment-request] After CR, evaluate if paymentRequest.id being a UUID is a must (#588) Marcos Cáceres
• Re: [w3c/payment-request] editorial: rewrite pay response details attr (#586) Marcos Cáceres
• Re: [w3c/payment-request] details attribute is incorrect (#575) Marcos Cáceres
• Re: [w3c/payment-request] editorial: rewrite pay response details attr (#586) Marcos Cáceres
• Re: [w3c/payment-request] editorial: rewrite pay response details attr (#586) Marcos Cáceres

Saturday, 19 August 2017

• Re: [w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201) Jinho Bang
• Re: [w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201) Jinho Bang

Friday, 18 August 2017

• Re: [w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201) ianbjacobs
• Re: [w3c/payment-request] editorial: rewrite pay response details attr (#586) ianbjacobs
• Re: [w3c/payment-request] details attribute is incorrect (#575) aboou2
• Re: [w3c/payment-request] details attribute is incorrect (#575) aboou2
• Re: [w3c/payment-request] Do not show payment requests for non-fully-active documents (#579) Marcos Cáceres
• Re: [w3c/payment-request] Do not show payment requests for non-fully-active documents (#579) Marcos Cáceres

Thursday, 17 August 2017

• Re: [w3c/payment-request] editorial: clarify currency member is alphabetic code (#587) Marcos Cáceres
• Re: [w3c/payment-request] Be more explicit that only alphabetic codes are supported for currency codes (#585) Marcos Cáceres
• Re: [w3c/payment-request] Drop array support for supported methods? (#549) Rick Byers

Wednesday, 16 August 2017

• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Marcos Cáceres
• Re: [w3c/payment-request] Real use case for .complete("unknown") - or mark "at risk" (#584) Marcos Cáceres
• Re: [w3c/payment-request] editorial: clarify currency member is alphabetic code (#587) Zach Koch
• [w3c/payment-request] editorial: clarify currency member is alphabetic code (#587) Marcos Cáceres
• [w3c/payment-request] editorial: rewrite pay response details attr (#586) Marcos Cáceres
• [w3c/payment-request] Be more explicit that only alphabetical codes are supported for currency codes (#585) Marcos Cáceres
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Dominique Hazael-Massieux
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Dominique Hazael-Massieux
• Re: [w3c/payment-request] Need short example of serializing response (#576) Marcos Cáceres
• Re: [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) Marcos Cáceres
• Re: [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) Marcos Cáceres
• Re: [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) Marcos Cáceres
• Re: [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) Marcos Cáceres
• [w3c/payment-request] Real use case for .complete("unknown") - or mark "at risk" (#584) Marcos Cáceres
• Re: [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) Marcos Cáceres
• Re: [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) Domenic Denicola
• Re: [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Relationship to PaymentRequest (#40) Marcos Cáceres
• Re: [w3c/payment-method-id] Editorial: final round of prep for CR (closes #39) (#45) Marcos Cáceres
• Re: [w3c/payment-method-id] CR checklist (#39) Marcos Cáceres
• Re: [w3c/payment-method-id] Editorial: final round of prep for CR (closes #39) (#45) Marcos Cáceres

Tuesday, 15 August 2017

• Re: [w3c/payment-method-basic-card] Relationship to PaymentRequest (#40) Rouslan Solomakhin
• [w3c/payment-method-basic-card] Relationship to PaymentRequest (#40) Rouslan Solomakhin
• Re: [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) Domenic Denicola
• Re: [w3c/payment-request] Do not show payment requests for non-fully-active documents (#579) ianbjacobs
• Re: [w3c/payment-request] Need to define the interaction of payment API with navigation and browsing context destruction (#360) ianbjacobs
• Re: [w3c/payment-method-id] Editorial: final round of prep for CR (closes #39) (#45) Marcos Cáceres
• Re: [w3c/payment-handler] Resolve with null instead of reject with 'SecurityError' if PaymentRequestEvent.openWindow is opened in a different origin (#202) Jinho Bang
• Re: [w3c/payment-method-id] Editorial: final round of prep for CR (closes #39) (#45) Marcos Cáceres
• Re: [w3c/payment-method-id] Editorial: final round of prep for CR (closes #39) (#45) Marcos Cáceres
• Re: [w3c/payment-handler] Resolve with null instead of reject with 'SecurityError' if PaymentRequestEvent.openWindow is opened in a different origin (#202) Jinho Bang
• [w3c/payment-method-id] Editorial: final round of prep for CR (closes #39) (#45) Marcos Cáceres
• Re: [w3c/payment-method-id] Reference manifest spec (#33) Marcos Cáceres
• Re: [w3c/payment-method-id] Define generalized PMI validator (#44) Marcos Cáceres
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) Marcos Cáceres
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) Marcos Cáceres
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) Marcos Cáceres
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) Marcos Cáceres
• Re: [w3c/payment-method-id] Define generalized PMI validator (#44) Marcos Cáceres
• [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) Marcos Cáceres
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Marcos Cáceres
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Marcos Cáceres
• Re: [w3c/payment-request] Need short example of serializing response (#576) Marcos Cáceres

Monday, 14 August 2017

• Re: [w3c/payment-request] Need short example of serializing response (#576) Marcos Cáceres
• Re: [w3c/payment-request] Need short example of serializing response (#576) Dave Longley
• Re: [w3c/payment-request] Need short example of serializing response (#576) Rouslan Solomakhin
• Re: [w3c/payment-request] Need short example of serializing response (#576) Dave Longley
• Re: [w3c/payment-request] Need short example of serializing response (#576) Rouslan Solomakhin
• Re: [w3c/payment-request] Do not show payment requests for non-fully-active documents (#579) Marcos Cáceres
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) Rouslan Solomakhin
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) gogerald
• Re: [w3c/payment-request] Do not show payment requests for non-fully-active documents (#579) Domenic Denicola
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Domenic Denicola
• Re: [w3c/payment-method-id] Define generalized PMI validator (#44) Domenic Denicola
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) gogerald
• Re: [w3c/payment-method-id] Define generalized PMI validator (#44) Rouslan Solomakhin
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) Rouslan Solomakhin
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) Rouslan Solomakhin
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) gogerald
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) gogerald
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) Marcos Cáceres
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) ianbjacobs
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) ianbjacobs
• Re: [w3c/payment-request] BREAKING CHANGE: change `supportedMethods` to DOMString (#551) Marcos Cáceres
• Re: [w3c/payment-request] BREAKING CHANGE: change `supportedMethods` to DOMString (#551) Simon Pieters
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) Adrian Hope-Bailie
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) Adrian Hope-Bailie
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Marcos Cáceres
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) Marcos Cáceres
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) Marcos Cáceres
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) Michael[tm] Smith
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) Marcos Cáceres
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) Marcos Cáceres
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) Marcos Cáceres
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) Marcos Cáceres
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) Marcos Cáceres

Saturday, 12 August 2017

• Re: [w3c/payment-method-basic-card] Define processing model (#39) Michael[tm] Smith
• Re: [w3c/payment-method-basic-card] Define processing model (#39) Michael[tm] Smith
• Re: [w3c/payment-method-basic-card] Define processing model (#39) Michael[tm] Smith
• Re: [w3c/payment-method-basic-card] Define processing model (#39) Michael[tm] Smith
• Re: [w3c/payment-method-basic-card] Define processing model (#39) Michael[tm] Smith
• Re: [w3c/payment-request] Drop array support for supported methods? (#549) Marcos Cáceres

Friday, 11 August 2017

• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) Jinho Bang
• Re: [w3c/payment-request] Drop array support for supported methods? (#549) Rick Byers
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) gogerald
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) gogerald
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) ianbjacobs
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Marcos Cáceres
• Re: [w3c/payment-request] Add section on Payment Handler Matching (#582) Marcos Cáceres
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Marcos Cáceres
• Re: [w3c/payment-request] Add section on Payment Handler Matching (#582) ianbjacobs
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) ianbjacobs
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Adrian Hope-Bailie
• Re: [w3c/payment-method-basic-card] Define processing model (#39) Marcos Cáceres
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) Jinho Bang
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) Jinho Bang
• Re: [w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201) Jinho Bang
• Re: [w3c/payment-handler] Add "Validate Methods Algorithm" (#197) Marcos Cáceres
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Marcos Cáceres
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Marcos Cáceres
• Re: [w3c/payment-request] Add section on Payment Handler Matching (#582) Marcos Cáceres
• Re: [w3c/payment-request] Add section on Payment Handler Matching (#582) Marcos Cáceres
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Say how we integrate with PaymentRequest (#23) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Say how we integrate with PaymentRequest (#23) Marcos Cáceres

Thursday, 10 August 2017

• Re: [w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201) gogerald
• Re: [w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201) gogerald
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) gogerald
• [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) gogerald
• Re: [w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201) Dave Longley
• [w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201) gogerald
• [w3c/payment-request] Add section on Payment Handler Matching (#582) ianbjacobs
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) Dominique Hazael-Massieux
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) Dominique Hazael-Massieux
• Re: [w3c/payment-request] Matching algo doesn't handle absence of filters (#532) Marcos Cáceres
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) Marcos Cáceres
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) Marcos Cáceres
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) Adrian Hope-Bailie
• Re: [w3c/payment-request] Dealing with "other" payment methods (#580) Anders Rundgren
• Re: [w3c/payment-method-basic-card] Define processing model (#39) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Define processing model (#39) Marcos Cáceres
• Re: [w3c/payment-request] Dealing with "other" payment methods (#580) Marcos Cáceres
• Re: [w3c/payment-request] Dealing with "other" payment methods (#580) Marcos Cáceres
• Re: [w3c/payment-request] Dealing with "other" payment methods (#580) Marcos Cáceres
• [w3c/payment-request] Validate PMIs, ignore duplicates (#581) Marcos Cáceres
• [w3c/payment-method-id] Define generalized PMI validator (#44) Marcos Cáceres
• [w3c/payment-request] Dealing with "other" payment methods (#580) Anders Rundgren
• Re: [w3c/payment-request] Use first matching PaymentDetailsModifier (#541) Marcos Cáceres
• Re: [w3c/payment-request] Use first matching PaymentDetailsModifier (#541) Marcos Cáceres
• Re: [w3c/payment-request] Use first matching PaymentDetailsModifier (#541) Marcos Cáceres
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) ianbjacobs
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) Marcos Cáceres
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) ianbjacobs
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) Marcos Cáceres
• Re: [w3c/payment-request] Do not show payment requests for non-fully-active documents (#579) Marcos Cáceres

Wednesday, 9 August 2017

• [w3c/payment-request] Do not show payment requests for non-fully-active documents (#579) Domenic Denicola
• Re: [w3c/payment-request] Need to define the interaction of payment API with navigation and browsing context destruction (#360) Domenic Denicola
• Re: [w3c/payment-handler] Registration example accesses `registration` before it is defined (#200) Dave Longley
• Re: [w3c/payment-handler] Registration example accesses `registration` before it is defined (#200) Dave Longley
• Re: [w3c/payment-handler] Registration example accesses `registration` before it is defined (#200) Dave Longley
• [w3c/payment-handler] Registration example accesses `registration` before it is defined (#200) Dave Longley
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Define processing model (#39) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Define processing model (#39) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Define processing model (#39) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Add text about why the api can reduce need to store credit card information (#18) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] No description of BasicCardResponse's billingAddress (#30) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] No description of BasicCardResponse's billingAddress (#30) Marcos Cáceres
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) Marcos Cáceres

Tuesday, 8 August 2017

• [w3c/webpayments-methods-tokenization] What to do if tokenized data looks like basic card data? (#21) ianbjacobs
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) ianbjacobs
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) Dave Longley
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) Adrian Hope-Bailie
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) Adrian Hope-Bailie
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) Adrian Hope-Bailie
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) Adrian Hope-Bailie
• Re: [w3c/payment-method-basic-card] WIP: Processing model (#39) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] WIP: Processing model (#39) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] WIP: Processing model (#39) Marcos Cáceres
• [w3c/payment-method-basic-card] WIP: Processing model (#39) Marcos Cáceres
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) Marcos Cáceres
• Re: [w3c/payment-request] Clarity required in section 21.2 regarding privacy (#475) Marcos Cáceres
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) Marcos Cáceres
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) Marcos Cáceres
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) ianbjacobs
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) Marcos Cáceres
• [w3c/payment-request] remove matching .data text from .show() (#578) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) Marcos Cáceres
• Re: [w3c/payment-request] What about billet payment option? (#577) ianbjacobs
• Re: [w3c/payment-request] What about billet payment option? (#577) ianbjacobs
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) ianbjacobs
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) Marcos Cáceres
• [w3c/payment-request] What about billet payment option? (#577) Mauricio

Monday, 7 August 2017

• Re: [w3c/payment-request] PaymentItem.pending can be true, but transaction can "complete" (#571) Marcos Cáceres
• Re: [w3c/payment-request] PaymentItem.pending can be true, but transaction can "complete" (#571) Marcos Cáceres
• Re: [w3c/payment-request] PaymentItem.pending can be true, but transaction can "complete" (#571) Zach Koch
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) Dave Longley
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) ianbjacobs
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) Anders Rundgren
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) Adrian Hope-Bailie
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) ianbjacobs
• Re: [w3c/payment-request] Clarity required in section 21.2 regarding privacy (#475) ianbjacobs
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) Adrian Hope-Bailie
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) Adrian Hope-Bailie
• Re: [w3c/payment-handler] `requestPermission` is static in Web IDL but example is not (#198) Adrian Hope-Bailie
• Re: [w3c/payment-handler] `requestPermission` is static in Web IDL but example is not (#198) Adrian Hope-Bailie
• Re: [w3c/payment-request] Clarity required in section 21.2 regarding privacy (#475) Marcos Cáceres
• [w3c/payment-request] Need short example of serializing response (#576) Marcos Cáceres
• Re: [w3c/payment-request] Clarity required in section 21.2 regarding privacy (#475) Marcos Cáceres
• Re: [w3c/payment-request] Clarity required in section 21.2 regarding privacy (#475) Marcos Cáceres
• [w3c/payment-request] details attribute is incorrect (#575) Marcos Cáceres
• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) Marcos Cáceres
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) Marcos Cáceres
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) Anders Rundgren
• Re: [w3c/payment-request] PaymentItem.pending can be true, but transaction can "complete" (#571) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) ianbjacobs
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) ianbjacobs
• Re: [w3c/payment-request] Change around payment handler language proposed by AHB (#574) Marcos Cáceres

Friday, 4 August 2017

• Re: [w3c/payment-request] Need to define the interaction of payment API with navigation and browsing context destruction (#360) Domenic Denicola
• Re: [w3c/payment-request] Support for "redirected" payment providers like PayPal, iDEAL/NL,Direktbetalning/SE etc (#573) ianbjacobs
• Re: [w3c/payment-request] Support for "redirected" payment providers like PayPal, iDEAL/NL,Direktbetalning/SE etc (#573) Anders Rundgren
• Re: [w3c/payment-handler] Fix a example for PaymentManager.requestPermission(). (#199) ianbjacobs
• Re: [w3c/payment-handler] Fix a example for PaymentManager.requestPermission(). (#199) ianbjacobs
• Re: [w3c/payment-handler] Fix a example for PaymentManager.requestPermission(). (#199) Dave Longley
• Re: [w3c/payment-handler] Fix a example for PaymentManager.requestPermission(). (#199) Jinho Bang
• [w3c/payment-handler] Fix a example for PaymentManager.requestPermission(). (#199) Jinho Bang

Thursday, 3 August 2017

• Re: [w3c/payment-request] Matching algo doesn't handle absence of filters (#532) ianbjacobs
• [w3c/payment-request] Change around payment handler language proposed by AHB (#574) ianbjacobs
• [w3c/payment-handler] `requestPermission` is static in Web IDL but example is not (#198) Dave Longley
• Re: [w3c/payment-handler] Add "Validate Methods Algorithm" (#197) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add "Validate Methods Algorithm" (#197) Rouslan Solomakhin
• Re: [w3c/payment-request] Support for "redirected" payment providers like PayPal, iDEAL/NL,Direktbetalning/SE etc (#573) ianbjacobs
• Re: [w3c/payment-request] Support for "redirected" payment providers like PayPal, iDEAL/NL,Direktbetalning/SE etc (#573) ianbjacobs
• Re: [w3c/payment-handler] Don't check PaymentRequest.[[state]] in openWindow() algorithm. (#196) Rouslan Solomakhin
• Re: [w3c/payment-request] Support for "redirected" payment providers like PayPal, iDEAL/NL,Direktbetalning/SE etc (#573) Rouslan Solomakhin
• [w3c/payment-request] Support for "redirected" payment providers like PayPal, iDEAL/NL,Direktbetalning/SE etc (#573) Anders Rundgren
• Re: [w3c/payment-handler] Don't check PaymentRequest.[[state]] in openWindow() algorithm. (#196) Jinho Bang
• Re: [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) Marcos Cáceres

Wednesday, 2 August 2017

• Re: [w3c/payment-request] Use first matching PaymentDetailsModifier (#541) Marcos Cáceres
• Re: [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) Marcos Cáceres
• Re: [w3c/payment-request] canMakePayment() needs to match .show() (#535) Marcos Cáceres
• Re: [w3c/payment-request] canMakePayment() needs to match .show() (#535) Zach Koch
• Re: [w3c/payment-request] Matching algo doesn't handle absence of filters (#532) Zach Koch
• Re: [w3c/payment-request] Aborting of in progress push payments (#473) Zach Koch
• Re: [w3c/payment-request] validate supportedMethods (#464) Zach Koch
• Re: [w3c/payment-request] Need to define the interaction of payment API with navigation and browsing context destruction (#360) Zach Koch
• Re: [w3c/payment-request] Use first matching PaymentDetailsModifier (#541) Zach Koch
• Re: [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) Zach Koch
• Re: [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) Marcos Cáceres
• Re: [w3c/payment-handler] Add "Validate Methods Algorithm" (#197) ianbjacobs
• Re: [w3c/payment-handler] Add "Validate Methods Algorithm" (#197) Rouslan Solomakhin
• [w3c/payment-handler] Add "Validate Methods Algorithm" (#197) Rouslan Solomakhin
• Re: [w3c/payment-handler] The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense (#192) gogerald
• Re: [w3c/payment-handler] Don't check PaymentRequest.[[state]] in openWindow() algorithm. (#196) ianbjacobs
• Re: [w3c/payment-handler] Don't check PaymentRequest.[[state]] in openWindow() algorithm. (#196) ianbjacobs
• Re: [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) Zach Koch
• Re: [w3c/payment-handler] The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense (#192) Marijn Kruisselbrink
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) Anders Rundgren
• Re: [w3c/payment-handler] The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense (#192) Rouslan Solomakhin
• [w3c/payment-handler] Don't check PaymentRequest.[[state]] in openWindow() algorithm. (#196) Rouslan Solomakhin
• Re: [w3c/payment-handler] The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense (#192) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) ianbjacobs
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) Anders Rundgren
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) Anders Rundgren
• Re: [w3c/payment-request] Considering allowing merchants to populate set of shipping addresses (#565) Marcos Cáceres
• Re: [w3c/payment-request] Considering allowing merchants to populate set of shipping addresses (#565) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) Anders Rundgren
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) Marcos Cáceres
• Re: [w3c/payment-request] Adding support for "encrypted basic card" (#572) Anders Rundgren
• [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) Anders Rundgren
• Re: [w3c/payment-request] Adding support for "encrypted basic card" (#572) Marcos Cáceres
• Re: [w3c/payment-request] Adding support for "encrypted basic card" (#572) Marcos Cáceres
• [w3c/payment-request] Adding support for "encrypted basic card" (#572) Anders Rundgren
• Re: [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) Marcos Cáceres
• Re: [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: test annotations (#570) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: test annotations (#570) Marcos Cáceres
• Re: [w3c/payment-request] Should user agent validate currency? (#490) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] Descriptions of change events attributes are somewhat misleading (#538) Marcos Cáceres
• Re: [w3c/payment-request] editorial: s/Event/PaymentRequestUpdateEvent (closes #538) (#569) Marcos Cáceres
• Re: [w3c/payment-request] Request `shippingType` attribute is not defined (#472) Marcos Cáceres
• Re: [w3c/payment-request] define PaymentRequest.shippingType attribute (#568) Marcos Cáceres
• Re: [w3c/payment-request] define PaymentRequest.shippingType attribute (#568) Marcos Cáceres
• Re: [w3c/payment-request] define PaymentRequest.shippingType attribute (#568) Marcos Cáceres
• Re: [w3c/payment-request] define PaymentRequest.shippingType attribute (#568) Marcos Cáceres
• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) ianbjacobs
• Re: [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) Rouslan Solomakhin
• [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Domenic Denicola

Tuesday, 1 August 2017

• Re: [w3c/payment-request] editorial: s/Event/PaymentRequestUpdateEvent (closes #538) (#569) Domenic Denicola
• Re: [w3c/payment-request] define PaymentRequest.shippingType attribute (#568) Domenic Denicola
• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) r12a
• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) ianbjacobs
• Re: [w3c/payment-request] Recipient and payerName are lacking i18n support (#471) r12a
• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) r12a
• Re: [w3c/payment-request] Add explicit extension point to matching algo (#470) Marcos Cáceres
• Re: [w3c/payment-request] Add explicit extension point to matching algo (#470) Marcos Cáceres
• Re: [w3c/payment-request] Add explicit extension point to matching algo (#470) ianbjacobs
• Re: [w3c/payment-request] Editorial: test annotations (#570) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: test annotations (#570) Marcos Cáceres
• [w3c/payment-request] Editorial: test annotations (#570) Marcos Cáceres
• Re: [w3c/payment-request] editorial: s/Event/PaymentRequestUpdateEvent (closes #538) (#569) Ben Tian
• [w3c/payment-request] editorial: s/Event/PaymentRequestUpdateEvent (closes #538) (#569) Marcos Cáceres
• [w3c/payment-request] define PaymentRequest.shippingType attribute (#568) Marcos Cáceres
• Re: [w3c/payment-request] Add explicit extension point to matching algo (#470) Marcos Cáceres
• Re: [w3c/webpayments-methods-tokenization] Should the response data include an "expires" field? (#12) Olivier Yiptong
• Re: [w3c/payment-request] Initial values for internal slots (#436) Marcos Cáceres
• Re: [w3c/payment-request] Initial values for internal slots (#436) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Marcos Cáceres
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) Domenic Denicola

Last message date: Thursday, 31 August 2017 23:28:20 UTC