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

aboou2

• Re: [w3c/payment-request] details attribute is incorrect (#575) (Friday, 18 August)
• Re: [w3c/payment-request] details attribute is incorrect (#575) (Friday, 18 August)

Ade Bateman

• Re: [w3c/payment-method-id] Define syntax of standard PMI (closes #48) (#49) (Thursday, 31 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Thursday, 31 August)
• Re: [w3c/payment-request] Empty shippingOptions (ab)used as error (#595) (Thursday, 31 August)
• Re: [w3c/payment-request] Empty shippingOptions (ab)used as error (#595) (Thursday, 31 August)
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, #595) (#596) (Thursday, 31 August)

Adrian Hope-Bailie

• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Wednesday, 23 August)
• Re: [w3c/payment-handler] Stop committing things without tests (#205) (Wednesday, 23 August)
• Re: [w3c/payment-handler] Stop committing things without tests (#205) (Wednesday, 23 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Monday, 21 August)
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) (Monday, 14 August)
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) (Monday, 14 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Friday, 11 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Thursday, 10 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Tuesday, 8 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Tuesday, 8 August)
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) (Tuesday, 8 August)
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) (Tuesday, 8 August)
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) (Monday, 7 August)
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Monday, 7 August)
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) (Monday, 7 August)
• Re: [w3c/payment-handler] `requestPermission` is static in Web IDL but example is not (#198) (Monday, 7 August)
• Re: [w3c/payment-handler] `requestPermission` is static in Web IDL but example is not (#198) (Monday, 7 August)

Anders Rundgren

• Re: [w3c/payment-request] Third party Method not recognized- why (#593) (Thursday, 24 August)
• Re: [w3c/payment-request] Dealing with "other" payment methods (#580) (Thursday, 10 August)
• [w3c/payment-request] Dealing with "other" payment methods (#580) (Thursday, 10 August)
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Monday, 7 August)
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Monday, 7 August)
• Re: [w3c/payment-request] Support for "redirected" payment providers like PayPal, iDEAL/NL,Direktbetalning/SE etc (#573) (Friday, 4 August)
• [w3c/payment-request] Support for "redirected" payment providers like PayPal, iDEAL/NL,Direktbetalning/SE etc (#573) (Thursday, 3 August)
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Wednesday, 2 August)
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Wednesday, 2 August)
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Wednesday, 2 August)
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Wednesday, 2 August)
• Re: [w3c/payment-request] Adding support for "encrypted basic card" (#572) (Wednesday, 2 August)
• [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Wednesday, 2 August)
• [w3c/payment-request] Adding support for "encrypted basic card" (#572) (Wednesday, 2 August)

Ben Tian

• Re: [w3c/payment-request] editorial: s/Event/PaymentRequestUpdateEvent (closes #538) (#569) (Tuesday, 1 August)

biseraivanovska

• [w3c/payment-request] Third party Method not recognized- why (#593) (Thursday, 24 August)

Dave Longley

• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Monday, 28 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] tweak about usage (93e90af) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• [w3c/payment-handler] Simplify Payment Handler Registration example. (#204) (Monday, 21 August)
• Re: [w3c/payment-request] Need short example of serializing response (#576) (Monday, 14 August)
• Re: [w3c/payment-request] Need short example of serializing response (#576) (Monday, 14 August)
• Re: [w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201) (Thursday, 10 August)
• Re: [w3c/payment-handler] Registration example accesses `registration` before it is defined (#200) (Wednesday, 9 August)
• Re: [w3c/payment-handler] Registration example accesses `registration` before it is defined (#200) (Wednesday, 9 August)
• Re: [w3c/payment-handler] Registration example accesses `registration` before it is defined (#200) (Wednesday, 9 August)
• [w3c/payment-handler] Registration example accesses `registration` before it is defined (#200) (Wednesday, 9 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Tuesday, 8 August)
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) (Monday, 7 August)
• Re: [w3c/payment-handler] Fix a example for PaymentManager.requestPermission(). (#199) (Friday, 4 August)
• [w3c/payment-handler] `requestPermission` is static in Web IDL but example is not (#198) (Thursday, 3 August)

Domenic Denicola

• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Thursday, 31 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 25 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 25 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Thursday, 24 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Thursday, 24 August)
• Re: [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) (Wednesday, 16 August)
• Re: [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) (Tuesday, 15 August)
• Re: [w3c/payment-request] Do not show payment requests for non-fully-active documents (#579) (Monday, 14 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Monday, 14 August)
• Re: [w3c/payment-method-id] Define generalized PMI validator (#44) (Monday, 14 August)
• [w3c/payment-request] Do not show payment requests for non-fully-active documents (#579) (Wednesday, 9 August)
• Re: [w3c/payment-request] Need to define the interaction of payment API with navigation and browsing context destruction (#360) (Wednesday, 9 August)
• Re: [w3c/payment-request] Need to define the interaction of payment API with navigation and browsing context destruction (#360) (Friday, 4 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Wednesday, 2 August)
• Re: [w3c/payment-request] editorial: s/Event/PaymentRequestUpdateEvent (closes #538) (#569) (Tuesday, 1 August)
• Re: [w3c/payment-request] define PaymentRequest.shippingType attribute (#568) (Tuesday, 1 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Tuesday, 1 August)

Dominique Hazael-Massieux

• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Wednesday, 16 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Wednesday, 16 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Thursday, 10 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Thursday, 10 August)

gogerald

• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) (Monday, 14 August)
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) (Monday, 14 August)
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) (Monday, 14 August)
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) (Monday, 14 August)
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) (Friday, 11 August)
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) (Friday, 11 August)
• Re: [w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201) (Thursday, 10 August)
• Re: [w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201) (Thursday, 10 August)
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) (Thursday, 10 August)
• [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) (Thursday, 10 August)
• [w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201) (Thursday, 10 August)
• Re: [w3c/payment-handler] The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense (#192) (Wednesday, 2 August)

ianbjacobs

• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Wednesday, 30 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Wednesday, 30 August)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Wednesday, 30 August)
• Re: [w3c/payment-handler] move dependency section down, as is done in PR API (#211) (Wednesday, 30 August)
• Re: [w3c/payment-handler] Add link to payment handler test suite (#210) (Wednesday, 30 August)
• Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157) (Tuesday, 29 August)
• Re: [w3c/payment-handler] Support for Abort() being delegated to Payment Handler (#117) (Tuesday, 29 August)
• [w3c/payment-handler] move dependency section down, as is done in PR API (#211) (Tuesday, 29 August)
• [w3c/payment-handler] Add link to payment handler test suite (#210) (Tuesday, 29 August)
• Re: [w3c/payment-handler] Make explicit which origin to use in conjunction with payment method manifest. (#209) (Tuesday, 29 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Tuesday, 29 August)
• Re: [w3c/payment-handler] Clarify empty instrument key meaning. (#208) (Monday, 28 August)
• Re: [w3c/payment-handler] Clarify empty instrument key meaning. (#208) (Monday, 28 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, ##595) (#596) (Friday, 25 August)
• Re: [w3c/webpayments-methods-tokenization] tokenProviderMerchantIdentifier vs merchantId (#18) (Tuesday, 22 August)
• Re: [w3c/webpayments-methods-tokenization] tokenProviderMerchantIdentifier vs merchantId (#18) (Tuesday, 22 August)
• Re: [w3c/payment-handler] Default handler icon? (#178) (Tuesday, 22 August)
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Tuesday, 22 August)
• Re: [w3c/payment-handler] Registration example accesses `registration` before it is defined (#200) (Tuesday, 22 August)
• Re: [w3c/payment-handler] Simplify Payment Handler Registration example. (#204) (Tuesday, 22 August)
• Re: [w3c/payment-handler] Registration example accesses `registration` before it is defined (#200) (Monday, 21 August)
• [w3c/payment-handler] Make explicit which origin to use in conjunction with payment method manifest (#203) (Monday, 21 August)
• Re: [w3c/webpayments-methods-tokenization] Wording of tokens used (#5) (Monday, 21 August)
• Re: [w3c/webpayments-methods-tokenization] Wording of tokens used (#5) (Monday, 21 August)
• Re: [w3c/webpayments-methods-tokenization] Structuring the tokenization payment method(s) (#13) (Monday, 21 August)
• Re: [w3c/webpayments-methods-tokenization] Structuring the tokenization payment method(s) (#13) (Monday, 21 August)
• Re: [w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201) (Friday, 18 August)
• Re: [w3c/payment-request] editorial: rewrite pay response details attr (#586) (Friday, 18 August)
• Re: [w3c/payment-request] Do not show payment requests for non-fully-active documents (#579) (Tuesday, 15 August)
• Re: [w3c/payment-request] Need to define the interaction of payment API with navigation and browsing context destruction (#360) (Tuesday, 15 August)
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) (Monday, 14 August)
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) (Monday, 14 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Friday, 11 August)
• Re: [w3c/payment-request] Add section on Payment Handler Matching (#582) (Friday, 11 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Friday, 11 August)
• [w3c/payment-request] Add section on Payment Handler Matching (#582) (Thursday, 10 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Thursday, 10 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Thursday, 10 August)
• [w3c/webpayments-methods-tokenization] What to do if tokenized data looks like basic card data? (#21) (Tuesday, 8 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Tuesday, 8 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Tuesday, 8 August)
• Re: [w3c/payment-request] What about billet payment option? (#577) (Tuesday, 8 August)
• Re: [w3c/payment-request] What about billet payment option? (#577) (Tuesday, 8 August)
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) (Tuesday, 8 August)
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Monday, 7 August)
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) (Monday, 7 August)
• Re: [w3c/payment-request] Clarity required in section 21.2 regarding privacy (#475) (Monday, 7 August)
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) (Monday, 7 August)
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) (Monday, 7 August)
• Re: [w3c/payment-request] Support for "redirected" payment providers like PayPal, iDEAL/NL,Direktbetalning/SE etc (#573) (Friday, 4 August)
• Re: [w3c/payment-handler] Fix a example for PaymentManager.requestPermission(). (#199) (Friday, 4 August)
• Re: [w3c/payment-handler] Fix a example for PaymentManager.requestPermission(). (#199) (Friday, 4 August)
• Re: [w3c/payment-request] Matching algo doesn't handle absence of filters (#532) (Thursday, 3 August)
• [w3c/payment-request] Change around payment handler language proposed by AHB (#574) (Thursday, 3 August)
• Re: [w3c/payment-request] Support for "redirected" payment providers like PayPal, iDEAL/NL,Direktbetalning/SE etc (#573) (Thursday, 3 August)
• Re: [w3c/payment-request] Support for "redirected" payment providers like PayPal, iDEAL/NL,Direktbetalning/SE etc (#573) (Thursday, 3 August)
• Re: [w3c/payment-handler] Add "Validate Methods Algorithm" (#197) (Wednesday, 2 August)
• Re: [w3c/payment-handler] Don't check PaymentRequest.[[state]] in openWindow() algorithm. (#196) (Wednesday, 2 August)
• Re: [w3c/payment-handler] Don't check PaymentRequest.[[state]] in openWindow() algorithm. (#196) (Wednesday, 2 August)
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Wednesday, 2 August)
• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Wednesday, 2 August)
• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Tuesday, 1 August)
• Re: [w3c/payment-request] Add explicit extension point to matching algo (#470) (Tuesday, 1 August)

Jinho Bang

• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) (Wednesday, 30 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Wednesday, 30 August)
• Re: [w3c/payment-handler] Add AbortPaymentEvent. (#207) (Wednesday, 30 August)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Wednesday, 30 August)
• Re: [w3c/payment-handler] Simplify Payment Handler Registration example. (#204) (Tuesday, 22 August)
• Re: [w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201) (Saturday, 19 August)
• Re: [w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201) (Saturday, 19 August)
• Re: [w3c/payment-handler] Resolve with null instead of reject with 'SecurityError' if PaymentRequestEvent.openWindow is opened in a different origin (#202) (Tuesday, 15 August)
• Re: [w3c/payment-handler] Resolve with null instead of reject with 'SecurityError' if PaymentRequestEvent.openWindow is opened in a different origin (#202) (Tuesday, 15 August)
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) (Friday, 11 August)
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) (Friday, 11 August)
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) (Friday, 11 August)
• Re: [w3c/payment-handler] Change openWindow algorithm 14.1 to 'Resolve promise with null.' (#201) (Friday, 11 August)
• Re: [w3c/payment-handler] Fix a example for PaymentManager.requestPermission(). (#199) (Friday, 4 August)
• [w3c/payment-handler] Fix a example for PaymentManager.requestPermission(). (#199) (Friday, 4 August)
• Re: [w3c/payment-handler] Don't check PaymentRequest.[[state]] in openWindow() algorithm. (#196) (Thursday, 3 August)

Marcos Cáceres

• Re: [w3c/payment-method-id] Define syntax of standard PMI (closes #48) (#49) (Thursday, 31 August)
• Re: [w3c/payment-method-id] Better defined validity of standardized PMIs? (#48) (Thursday, 31 August)
• Re: [w3c/payment-method-id] Define syntax of standard PMI (closes #48) (#49) (Thursday, 31 August)
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, #595) (#596) (Thursday, 31 August)
• Re: [w3c/payment-request] l10n: adds Localizable dict + TextDirection enum (#455) (Thursday, 31 August)
• Re: [w3c/payment-request] l10n: adds Localizable dict + TextDirection enum (#455) (Thursday, 31 August)
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, #595) (#596) (Thursday, 31 August)
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, #595) (#596) (Thursday, 31 August)
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, #595) (#596) (Thursday, 31 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Thursday, 31 August)
• Re: [w3c/payment-request] Behavior for multiple modifiers for the same payment method is not defined (#309) (Thursday, 31 August)
• Re: [w3c/payment-request] validate supportedMethods (#464) (Thursday, 31 August)
• Re: [w3c/payment-method-id] Other specs must define validity rules (closes #46) (#47) (Thursday, 31 August)
• Re: [w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46) (Thursday, 31 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Thursday, 31 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Thursday, 31 August)
• Re: [w3c/payment-method-id] Better defined validity of standardized PMIs? (#48) (Wednesday, 30 August)
• Re: [w3c/payment-handler] Add AbortPaymentEvent. (#207) (Wednesday, 30 August)
• Re: [w3c/payment-handler] Add link to payment handler test suite (#210) (Wednesday, 30 August)
• Re: [w3c/payment-handler] move dependency section down, as is done in PR API (#211) (Wednesday, 30 August)
• Re: [w3c/payment-handler] Establish Editorial process (#156) (Wednesday, 30 August)
• [w3c/payment-method-id] Define syntax of standard PMI (closes #48) (#49) (Wednesday, 30 August)
• [w3c/payment-method-id] Better define validity of standardized PMIs? (#48) (Wednesday, 30 August)
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, #595) (#596) (Tuesday, 29 August)
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, #595) (#596) (Tuesday, 29 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Monday, 28 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Monday, 28 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Monday, 28 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Monday, 28 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Monday, 28 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Monday, 28 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Monday, 28 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Monday, 28 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Monday, 28 August)
• Re: [w3c/payment-request] https://www.w3.org/TR/payment-request/#conditional-modifications-to-payment-request (#597) (Saturday, 26 August)
• Re: [w3c/payment-request] https://www.w3.org/TR/payment-request/#conditional-modifications-to-payment-request (#597) (Saturday, 26 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Saturday, 26 August)
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, ##595) (#596) (Friday, 25 August)
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, ##595) (#596) (Friday, 25 August)
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (closes #594, ##595) (#596) (Friday, 25 August)
• Re: [w3c/payment-request] Throw on dup shippingOptions (closes #594, ##595) (#596) (Friday, 25 August)
• [w3c/payment-request] Throw on dup shippingOptions (closes #594, ##595) (#596) (Friday, 25 August)
• Re: [w3c/payment-request] Duplicate shippingOptions lead to inconsistent `updateWith()` - should throw! (#594) (Friday, 25 August)
• Re: [w3c/payment-request] Empty shippingOptions (ab)used as error (#595) (Friday, 25 August)
• Re: [w3c/payment-request] Empty shippingOptions (ab)used as error (#595) (Friday, 25 August)
• [w3c/payment-request] Empty shippingOptions (ab)used as error (#595) (Friday, 25 August)
• [w3c/payment-request] Duplicate shippingOptions lead to inconsistent `updateWith()` - should throw! (#594) (Friday, 25 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 25 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 25 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 25 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 25 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 25 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 25 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 25 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 25 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 25 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 25 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 25 August)
• Re: [w3c/payment-method-basic-card] Relationship to PaymentRequest (#40) (Thursday, 24 August)
• Re: [w3c/payment-request] Third party Method not recognized- why (#593) (Thursday, 24 August)
• Re: [w3c/payment-request] Third party Method not recognized- why (#593) (Thursday, 24 August)
• Re: [w3c/payment-method-id] Other specs must define validity rules (closes #46) (#47) (Thursday, 24 August)
• [w3c/payment-method-id] Other specs must define validity rules (closes #46) (#47) (Thursday, 24 August)
• Re: [w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46) (Wednesday, 23 August)
• Re: [w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46) (Wednesday, 23 August)
• Re: [w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46) (Wednesday, 23 August)
• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) (Wednesday, 23 August)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Wednesday, 23 August)
• [w3c/payment-handler] Stop committing things without tests (#205) (Wednesday, 23 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Wednesday, 23 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Wednesday, 23 August)
• [w3c/payment-request] Consider adding some means of getting the details out of a payment request (#592) (Wednesday, 23 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Tuesday, 22 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Tuesday, 22 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Tuesday, 22 August)
• [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Tuesday, 22 August)
• Re: [w3c/payment-request] Don't block UI if .updateWith() not called (closes #589) (#590) (Tuesday, 22 August)
• Re: [w3c/payment-request] Don't block UI if .updateWith() not called (closes #589) (#590) (Tuesday, 22 August)
• Re: [w3c/payment-request] Don't block UI if .updateWith() not called (closes #589) (#590) (Tuesday, 22 August)
• [w3c/payment-request] Don't block UI if .updateWith() not called (closes #589) (#590) (Tuesday, 22 August)
• Re: [w3c/payment-request] .updateWith() should only be callable if event was canceled (#589) (Tuesday, 22 August)
• [w3c/payment-request] .updateWith() should only be callable if event was cancelled (#589) (Tuesday, 22 August)
• Re: [w3c/payment-request] Real use case for .complete("unknown") - or mark "at risk" (#584) (Monday, 21 August)
• Re: [w3c/payment-request] After CR, evaluate if paymentRequest.id being a UUID is a must (#588) (Monday, 21 August)
• [w3c/payment-request] After CR, evaluate if paymentRequest.id being a UUID is a must (#588) (Monday, 21 August)
• Re: [w3c/payment-request] editorial: rewrite pay response details attr (#586) (Monday, 21 August)
• Re: [w3c/payment-request] details attribute is incorrect (#575) (Monday, 21 August)
• Re: [w3c/payment-request] editorial: rewrite pay response details attr (#586) (Monday, 21 August)
• Re: [w3c/payment-request] editorial: rewrite pay response details attr (#586) (Monday, 21 August)
• Re: [w3c/payment-request] Do not show payment requests for non-fully-active documents (#579) (Friday, 18 August)
• Re: [w3c/payment-request] Do not show payment requests for non-fully-active documents (#579) (Friday, 18 August)
• Re: [w3c/payment-request] editorial: clarify currency member is alphabetic code (#587) (Thursday, 17 August)
• Re: [w3c/payment-request] Be more explicit that only alphabetic codes are supported for currency codes (#585) (Thursday, 17 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Wednesday, 16 August)
• Re: [w3c/payment-request] Real use case for .complete("unknown") - or mark "at risk" (#584) (Wednesday, 16 August)
• [w3c/payment-request] editorial: clarify currency member is alphabetic code (#587) (Wednesday, 16 August)
• [w3c/payment-request] editorial: rewrite pay response details attr (#586) (Wednesday, 16 August)
• [w3c/payment-request] Be more explicit that only alphabetical codes are supported for currency codes (#585) (Wednesday, 16 August)
• Re: [w3c/payment-request] Need short example of serializing response (#576) (Wednesday, 16 August)
• Re: [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) (Wednesday, 16 August)
• Re: [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) (Wednesday, 16 August)
• Re: [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) (Wednesday, 16 August)
• Re: [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) (Wednesday, 16 August)
• [w3c/payment-request] Real use case for .complete("unknown") - or mark "at risk" (#584) (Wednesday, 16 August)
• Re: [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) (Wednesday, 16 August)
• Re: [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) (Wednesday, 16 August)
• Re: [w3c/payment-method-basic-card] Relationship to PaymentRequest (#40) (Wednesday, 16 August)
• Re: [w3c/payment-method-id] Editorial: final round of prep for CR (closes #39) (#45) (Wednesday, 16 August)
• Re: [w3c/payment-method-id] CR checklist (#39) (Wednesday, 16 August)
• Re: [w3c/payment-method-id] Editorial: final round of prep for CR (closes #39) (#45) (Wednesday, 16 August)
• Re: [w3c/payment-method-id] Editorial: final round of prep for CR (closes #39) (#45) (Tuesday, 15 August)
• Re: [w3c/payment-method-id] Editorial: final round of prep for CR (closes #39) (#45) (Tuesday, 15 August)
• Re: [w3c/payment-method-id] Editorial: final round of prep for CR (closes #39) (#45) (Tuesday, 15 August)
• [w3c/payment-method-id] Editorial: final round of prep for CR (closes #39) (#45) (Tuesday, 15 August)
• Re: [w3c/payment-method-id] Reference manifest spec (#33) (Tuesday, 15 August)
• Re: [w3c/payment-method-id] Define generalized PMI validator (#44) (Tuesday, 15 August)
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) (Tuesday, 15 August)
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) (Tuesday, 15 August)
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) (Tuesday, 15 August)
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) (Tuesday, 15 August)
• Re: [w3c/payment-method-id] Define generalized PMI validator (#44) (Tuesday, 15 August)
• [w3c/payment-request] editorial: add example of .toJSON()+fetch POST (#583) (Tuesday, 15 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Tuesday, 15 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Tuesday, 15 August)
• Re: [w3c/payment-request] Need short example of serializing response (#576) (Tuesday, 15 August)
• Re: [w3c/payment-request] Need short example of serializing response (#576) (Monday, 14 August)
• Re: [w3c/payment-request] Do not show payment requests for non-fully-active documents (#579) (Monday, 14 August)
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) (Monday, 14 August)
• Re: [w3c/payment-request] BREAKING CHANGE: change `supportedMethods` to DOMString (#551) (Monday, 14 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Monday, 14 August)
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) (Monday, 14 August)
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) (Monday, 14 August)
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) (Monday, 14 August)
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) (Monday, 14 August)
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) (Monday, 14 August)
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) (Monday, 14 August)
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) (Monday, 14 August)
• Re: [w3c/payment-request] Drop array support for supported methods? (#549) (Saturday, 12 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Friday, 11 August)
• Re: [w3c/payment-request] Add section on Payment Handler Matching (#582) (Friday, 11 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Friday, 11 August)
• Re: [w3c/payment-method-basic-card] Define processing model (#39) (Friday, 11 August)
• Re: [w3c/payment-handler] Add "Validate Methods Algorithm" (#197) (Friday, 11 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Friday, 11 August)
• Re: [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Friday, 11 August)
• Re: [w3c/payment-request] Add section on Payment Handler Matching (#582) (Friday, 11 August)
• Re: [w3c/payment-request] Add section on Payment Handler Matching (#582) (Friday, 11 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Friday, 11 August)
• Re: [w3c/payment-method-basic-card] Say how we integrate with PaymentRequest (#23) (Friday, 11 August)
• Re: [w3c/payment-method-basic-card] Say how we integrate with PaymentRequest (#23) (Friday, 11 August)
• Re: [w3c/payment-request] Matching algo doesn't handle absence of filters (#532) (Thursday, 10 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Thursday, 10 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Thursday, 10 August)
• Re: [w3c/payment-method-basic-card] Define processing model (#39) (Thursday, 10 August)
• Re: [w3c/payment-method-basic-card] Define processing model (#39) (Thursday, 10 August)
• Re: [w3c/payment-request] Dealing with "other" payment methods (#580) (Thursday, 10 August)
• Re: [w3c/payment-request] Dealing with "other" payment methods (#580) (Thursday, 10 August)
• Re: [w3c/payment-request] Dealing with "other" payment methods (#580) (Thursday, 10 August)
• [w3c/payment-request] Validate PMIs, ignore duplicates (#581) (Thursday, 10 August)
• [w3c/payment-method-id] Define generalized PMI validator (#44) (Thursday, 10 August)
• Re: [w3c/payment-request] Use first matching PaymentDetailsModifier (#541) (Thursday, 10 August)
• Re: [w3c/payment-request] Use first matching PaymentDetailsModifier (#541) (Thursday, 10 August)
• Re: [w3c/payment-request] Use first matching PaymentDetailsModifier (#541) (Thursday, 10 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Thursday, 10 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Thursday, 10 August)
• Re: [w3c/payment-request] Do not show payment requests for non-fully-active documents (#579) (Thursday, 10 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Wednesday, 9 August)
• Re: [w3c/payment-method-basic-card] Define processing model (#39) (Wednesday, 9 August)
• Re: [w3c/payment-method-basic-card] Define processing model (#39) (Wednesday, 9 August)
• Re: [w3c/payment-method-basic-card] Define processing model (#39) (Wednesday, 9 August)
• Re: [w3c/payment-method-basic-card] Add text about why the api can reduce need to store credit card information (#18) (Wednesday, 9 August)
• Re: [w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36) (Wednesday, 9 August)
• Re: [w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36) (Wednesday, 9 August)
• Re: [w3c/payment-method-basic-card] No description of BasicCardResponse's billingAddress (#30) (Wednesday, 9 August)
• Re: [w3c/payment-method-basic-card] No description of BasicCardResponse's billingAddress (#30) (Wednesday, 9 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Wednesday, 9 August)
• Re: [w3c/payment-method-basic-card] WIP: Processing model (#39) (Tuesday, 8 August)
• Re: [w3c/payment-method-basic-card] WIP: Processing model (#39) (Tuesday, 8 August)
• Re: [w3c/payment-method-basic-card] WIP: Processing model (#39) (Tuesday, 8 August)
• [w3c/payment-method-basic-card] WIP: Processing model (#39) (Tuesday, 8 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Tuesday, 8 August)
• Re: [w3c/payment-request] Clarity required in section 21.2 regarding privacy (#475) (Tuesday, 8 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Tuesday, 8 August)
• Re: [w3c/payment-request] remove matching .data text from .show() (#578) (Tuesday, 8 August)
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) (Tuesday, 8 August)
• [w3c/payment-request] remove matching .data text from .show() (#578) (Tuesday, 8 August)
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) (Tuesday, 8 August)
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) (Tuesday, 8 August)
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) (Tuesday, 8 August)
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) (Tuesday, 8 August)
• Re: [w3c/payment-request] PaymentItem.pending can be true, but transaction can "complete" (#571) (Monday, 7 August)
• Re: [w3c/payment-request] PaymentItem.pending can be true, but transaction can "complete" (#571) (Monday, 7 August)
• Re: [w3c/payment-request] Clarity required in section 21.2 regarding privacy (#475) (Monday, 7 August)
• [w3c/payment-request] Need short example of serializing response (#576) (Monday, 7 August)
• Re: [w3c/payment-request] Clarity required in section 21.2 regarding privacy (#475) (Monday, 7 August)
• Re: [w3c/payment-request] Clarity required in section 21.2 regarding privacy (#475) (Monday, 7 August)
• [w3c/payment-request] details attribute is incorrect (#575) (Monday, 7 August)
• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Monday, 7 August)
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) (Monday, 7 August)
• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) (Monday, 7 August)
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Monday, 7 August)
• Re: [w3c/payment-request] PaymentItem.pending can be true, but transaction can "complete" (#571) (Monday, 7 August)
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Monday, 7 August)
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Monday, 7 August)
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) (Monday, 7 August)
• Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574) (Monday, 7 August)
• Re: [w3c/payment-request] Change around payment handler language proposed by AHB (#574) (Monday, 7 August)
• Re: [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) (Thursday, 3 August)
• Re: [w3c/payment-request] Use first matching PaymentDetailsModifier (#541) (Wednesday, 2 August)
• Re: [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) (Wednesday, 2 August)
• Re: [w3c/payment-request] canMakePayment() needs to match .show() (#535) (Wednesday, 2 August)
• Re: [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) (Wednesday, 2 August)
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Wednesday, 2 August)
• Re: [w3c/payment-request] Considering allowing merchants to populate set of shipping addresses (#565) (Wednesday, 2 August)
• Re: [w3c/payment-request] Considering allowing merchants to populate set of shipping addresses (#565) (Wednesday, 2 August)
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Wednesday, 2 August)
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Wednesday, 2 August)
• Re: [w3c/payment-method-basic-card] Adding support for "encrypted basic card" (#38) (Wednesday, 2 August)
• Re: [w3c/payment-request] Adding support for "encrypted basic card" (#572) (Wednesday, 2 August)
• Re: [w3c/payment-request] Adding support for "encrypted basic card" (#572) (Wednesday, 2 August)
• Re: [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) (Wednesday, 2 August)
• Re: [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) (Wednesday, 2 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Wednesday, 2 August)
• Re: [w3c/payment-request] Editorial: test annotations (#570) (Wednesday, 2 August)
• Re: [w3c/payment-request] Editorial: test annotations (#570) (Wednesday, 2 August)
• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Wednesday, 2 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Wednesday, 2 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Wednesday, 2 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Wednesday, 2 August)
• Re: [w3c/payment-request] Descriptions of change events attributes are somewhat misleading (#538) (Wednesday, 2 August)
• Re: [w3c/payment-request] editorial: s/Event/PaymentRequestUpdateEvent (closes #538) (#569) (Wednesday, 2 August)
• Re: [w3c/payment-request] Request `shippingType` attribute is not defined (#472) (Wednesday, 2 August)
• Re: [w3c/payment-request] define PaymentRequest.shippingType attribute (#568) (Wednesday, 2 August)
• Re: [w3c/payment-request] define PaymentRequest.shippingType attribute (#568) (Wednesday, 2 August)
• Re: [w3c/payment-request] define PaymentRequest.shippingType attribute (#568) (Wednesday, 2 August)
• Re: [w3c/payment-request] define PaymentRequest.shippingType attribute (#568) (Wednesday, 2 August)
• [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) (Wednesday, 2 August)
• Re: [w3c/payment-request] Add explicit extension point to matching algo (#470) (Tuesday, 1 August)
• Re: [w3c/payment-request] Add explicit extension point to matching algo (#470) (Tuesday, 1 August)
• Re: [w3c/payment-request] Editorial: test annotations (#570) (Tuesday, 1 August)
• Re: [w3c/payment-request] Editorial: test annotations (#570) (Tuesday, 1 August)
• [w3c/payment-request] Editorial: test annotations (#570) (Tuesday, 1 August)
• [w3c/payment-request] editorial: s/Event/PaymentRequestUpdateEvent (closes #538) (#569) (Tuesday, 1 August)
• [w3c/payment-request] define PaymentRequest.shippingType attribute (#568) (Tuesday, 1 August)
• Re: [w3c/payment-request] Add explicit extension point to matching algo (#470) (Tuesday, 1 August)
• Re: [w3c/payment-request] Initial values for internal slots (#436) (Tuesday, 1 August)
• Re: [w3c/payment-request] Initial values for internal slots (#436) (Tuesday, 1 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Tuesday, 1 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Tuesday, 1 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Tuesday, 1 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Tuesday, 1 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Tuesday, 1 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Tuesday, 1 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Tuesday, 1 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Tuesday, 1 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Tuesday, 1 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Tuesday, 1 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Tuesday, 1 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Tuesday, 1 August)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Tuesday, 1 August)

Marijn Kruisselbrink

• Re: [w3c/payment-handler] The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense (#192) (Wednesday, 2 August)

Mauricio

• [w3c/payment-request] What about billet payment option? (#577) (Tuesday, 8 August)

Michael[tm] Smith

• Re: [w3c/payment-method-id] editorial: add CR exit criteria (#42) (Monday, 14 August)
• Re: [w3c/payment-method-basic-card] Define processing model (#39) (Saturday, 12 August)
• Re: [w3c/payment-method-basic-card] Define processing model (#39) (Saturday, 12 August)
• Re: [w3c/payment-method-basic-card] Define processing model (#39) (Saturday, 12 August)
• Re: [w3c/payment-method-basic-card] Define processing model (#39) (Saturday, 12 August)
• Re: [w3c/payment-method-basic-card] Define processing model (#39) (Saturday, 12 August)

Moe Ahmadi

• Re: [w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46) (Wednesday, 23 August)
• Re: [w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46) (Wednesday, 23 August)
• [w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46) (Wednesday, 23 August)

Olivier Yiptong

• Re: [w3c/webpayments-methods-tokenization] Should the response data include an "expires" field? (#12) (Tuesday, 1 August)

Philip Jägenstedt

• Re: [w3c/payment-method-basic-card] Relationship to PaymentRequest (#40) (Thursday, 24 August)

r12a

• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Tuesday, 1 August)
• Re: [w3c/payment-request] Recipient and payerName are lacking i18n support (#471) (Tuesday, 1 August)
• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Tuesday, 1 August)

Rick Byers

• Re: [w3c/payment-request] Drop array support for supported methods? (#549) (Thursday, 17 August)
• Re: [w3c/payment-request] Drop array support for supported methods? (#549) (Friday, 11 August)

Rouslan Solomakhin

• Re: [w3c/payment-handler] Add AbortPaymentEvent. (#207) (Wednesday, 30 August)
• Re: [w3c/payment-method-id] Better defined validity of standardized PMIs? (#48) (Wednesday, 30 August)
• Re: [w3c/payment-handler] Add AbortPaymentEvent. (#207) (Tuesday, 29 August)
• [w3c/payment-handler] Make explicit which origin to use in conjunction with payment method manifest. (#209) (Monday, 28 August)
• Re: [w3c/payment-handler] Clarify empty instrument key meaning. (#208) (Monday, 28 August)
• [w3c/payment-handler] Clarify empty instrument key meaning. (#208) (Monday, 28 August)
• [w3c/payment-handler] Add AbortPaymentEvent. (#207) (Monday, 28 August)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Monday, 28 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Friday, 25 August)
• Re: [w3c/payment-request] Third party Method not recognized- why (#593) (Thursday, 24 August)
• Re: [w3c/payment-method-id] w3c.github.io/payment-method-id/ is not in parity with the tests (#46) (Wednesday, 23 August)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Monday, 21 August)
• Re: [w3c/payment-handler] The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense (#192) (Monday, 21 August)
• Re: [w3c/payment-handler] The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense (#192) (Monday, 21 August)
• Re: [w3c/payment-handler] Add "Validate Methods Algorithm" (#197) (Monday, 21 August)
• Re: [w3c/payment-handler] Add "Validate Methods Algorithm" (#197) (Monday, 21 August)
• Re: [w3c/payment-method-basic-card] Relationship to PaymentRequest (#40) (Tuesday, 15 August)
• [w3c/payment-method-basic-card] Relationship to PaymentRequest (#40) (Tuesday, 15 August)
• Re: [w3c/payment-request] Need short example of serializing response (#576) (Monday, 14 August)
• Re: [w3c/payment-request] Need short example of serializing response (#576) (Monday, 14 August)
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) (Monday, 14 August)
• Re: [w3c/payment-method-id] Define generalized PMI validator (#44) (Monday, 14 August)
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) (Monday, 14 August)
• Re: [w3c/payment-handler] Return null after the window is opened instead of reject with 'SecurityError' (#202) (Monday, 14 August)
• Re: [w3c/payment-handler] Add "Validate Methods Algorithm" (#197) (Thursday, 3 August)
• Re: [w3c/payment-handler] Add "Validate Methods Algorithm" (#197) (Thursday, 3 August)
• Re: [w3c/payment-handler] Don't check PaymentRequest.[[state]] in openWindow() algorithm. (#196) (Thursday, 3 August)
• Re: [w3c/payment-request] Support for "redirected" payment providers like PayPal, iDEAL/NL,Direktbetalning/SE etc (#573) (Thursday, 3 August)
• Re: [w3c/payment-handler] Add "Validate Methods Algorithm" (#197) (Wednesday, 2 August)
• [w3c/payment-handler] Add "Validate Methods Algorithm" (#197) (Wednesday, 2 August)
• Re: [w3c/payment-handler] The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense (#192) (Wednesday, 2 August)
• [w3c/payment-handler] Don't check PaymentRequest.[[state]] in openWindow() algorithm. (#196) (Wednesday, 2 August)
• Re: [w3c/payment-handler] The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense (#192) (Wednesday, 2 August)
• Re: [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) (Wednesday, 2 August)

sabrinatseng

• [w3c/payment-request] https://www.w3.org/TR/payment-request/#conditional-modifications-to-payment-request (#597) (Saturday, 26 August)

Simon Pieters

• Re: [w3c/payment-request] BREAKING CHANGE: change `supportedMethods` to DOMString (#551) (Monday, 14 August)

Zach Koch

• Re: [w3c/payment-request] Throw on dup shippingOptions ids (#596) (Thursday, 31 August)
• Re: [w3c/payment-method-id] Define syntax of standard PMI (closes #48) (#49) (Thursday, 31 August)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 25 August)
• Re: [w3c/payment-request] Real use case for .complete("unknown") - or mark "at risk" (#584) (Monday, 21 August)
• Re: [w3c/payment-request] editorial: clarify currency member is alphabetic code (#587) (Wednesday, 16 August)
• Re: [w3c/payment-request] PaymentItem.pending can be true, but transaction can "complete" (#571) (Monday, 7 August)
• Re: [w3c/payment-request] canMakePayment() needs to match .show() (#535) (Wednesday, 2 August)
• Re: [w3c/payment-request] Matching algo doesn't handle absence of filters (#532) (Wednesday, 2 August)
• Re: [w3c/payment-request] Aborting of in progress push payments (#473) (Wednesday, 2 August)
• Re: [w3c/payment-request] validate supportedMethods (#464) (Wednesday, 2 August)
• Re: [w3c/payment-request] Need to define the interaction of payment API with navigation and browsing context destruction (#360) (Wednesday, 2 August)
• Re: [w3c/payment-request] Use first matching PaymentDetailsModifier (#541) (Wednesday, 2 August)
• Re: [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) (Wednesday, 2 August)
• Re: [w3c/payment-request] Should PaymentItem.pending be marked "at risk"? (#571) (Wednesday, 2 August)

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