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

adamroach

• Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521) (Tuesday, 9 May)

Ade Bateman

• Re: [w3c/browser-payment-api] editorial: mark currencySystem at risk (#522) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] editorial: add link to test suite (#519) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] Add extension point (#492) (Wednesday, 10 May)

Adrian Hope-Bailie

• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Sunday, 28 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23) (Thursday, 25 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/payment-handler] Added "github" param for respec (#161) (Tuesday, 16 May)
• Re: [w3c/browser-payment-api] editorial: destructure tuple (closes #498) (#530) (Tuesday, 16 May)
• [w3c/browser-payment-api] Matching algo doesn't handle (#532) (Tuesday, 16 May)
• Re: [w3c/payment-handler] Link fixes (#160) (Monday, 15 May)
• Re: [w3c/payment-handler] link fixes (#159) (Monday, 15 May)
• Re: [w3c/browser-payment-api] editorial: destructure tuple (closes #498) (#530) (Monday, 15 May)
• Re: [w3c/payment-handler] Establish Editorial process (#156) (Friday, 12 May)
• Re: [w3c/payment-handler] Establish Editorial process (#156) (Friday, 12 May)
• Re: [w3c/payment-handler] Pre FPWD tweaks (#155) (Thursday, 11 May)
• Re: [w3c/payment-handler] Update README.md (#154) (Thursday, 11 May)
• Re: [w3c/browser-payment-api] Add extension point (#492) (Thursday, 11 May)
• Re: [w3c/browser-payment-api] Add extension point (#492) (Thursday, 11 May)
• Re: [w3c/browser-payment-api] Add explicit extension point to matching algo (#470) (Thursday, 11 May)
• Re: [w3c/browser-payment-api] Add extension point (#492) (Thursday, 11 May)
• Re: [w3c/browser-payment-api] Add extension point (#492) (Thursday, 11 May)
• Re: [w3c/browser-payment-api] Add extension point (#492) (Thursday, 11 May)
• Re: [w3c/webpayments-payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Wednesday, 10 May)
• Re: [w3c/webpayments-payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521) (Tuesday, 9 May)
• Re: [w3c/webpayments-payment-handler] Spec still talks about "payment app" (#151) (Tuesday, 9 May)
• Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521) (Tuesday, 9 May)
• Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521) (Tuesday, 9 May)
• Re: [w3c/webpayments-payment-handler] Spec still talks about "payment app" (#151) (Tuesday, 9 May)
• [w3c/browser-payment-api] Is PaymentResponse.details the result of a JSON.parse() (#526) (Monday, 8 May)
• Re: [w3c/webpayments-payment-handler] Update LICENSE.md (#146) (Thursday, 4 May)
• Re: [w3c/webpayments-payment-handler] Fix wrt group charter (#147) (Thursday, 4 May)
• Re: [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143) (Wednesday, 3 May)
• Re: [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143) (Wednesday, 3 May)
• Re: [w3c/browser-payment-api] editorial: mark currencySystem at risk (#522) (Wednesday, 3 May)
• Re: [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523) (Wednesday, 3 May)
• Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521) (Wednesday, 3 May)
• Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521) (Wednesday, 3 May)
• Re: [w3c/webpayments-payment-handler] Fix to prevent duplicate ids by respec (#145) (Wednesday, 3 May)
• Re: [w3c/webpayments-payment-handler] Fix to prevent duplicate ids by respec (#145) (Wednesday, 3 May)
• Re: [w3c/webpayments-payment-handler] Merge PaymentAppRequest and PaymentRequestEvent (#144) (Tuesday, 2 May)
• [w3c/webpayments-payment-handler] Merge PaymentAppRequest and PaymentRequestEvent (#144) (Tuesday, 2 May)

Ben Tian

• Re: [w3c/browser-payment-api] shippingOption description is misleading (#534) (Friday, 26 May)
• Re: [w3c/browser-payment-api] editorial: s/web page/developers (#527) (Wednesday, 10 May)
• [w3c/browser-payment-api] editorial: s/web page/developers and s/the developer/developers (#527) (Tuesday, 9 May)
• [w3c/browser-payment-api] editorial: s/payment app/payment handler (#525) (Monday, 8 May)

Dave Longley

• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Friday, 26 May)
• Re: [w3c/webpayments-payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Wednesday, 10 May)
• [w3c/webpayments-payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Wednesday, 10 May)

Domenic Denicola

• Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540) (Monday, 29 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/browser-payment-api] editorial: cleanup of updateWith() (#533) (Tuesday, 23 May)
• Re: [w3c/browser-payment-api] editorial: cleanup of updateWith() (#533) (Monday, 22 May)
• Re: [w3c/browser-payment-api] editorial: s/throw/reject in complete() (closes #509) (#529) (Monday, 15 May)
• Re: [w3c/browser-payment-api] editorial: s/characters/code points (closes #322) (#528) (Monday, 15 May)
• Re: [w3c/browser-payment-api] editorial: rephrase parse, rethrow, or null otherwise (closes #458) (#531) (Monday, 15 May)
• Re: [w3c/browser-payment-api] editorial: destructure tuple (closes #498) (#530) (Monday, 15 May)
• Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] editorial: mark currencySystem at risk (#522) (Wednesday, 3 May)

Dominique Hazael-Massieux

• Re: [w3c/browser-payment-api] editorial: s/web page/developers and s/the developer/developers (#527) (Tuesday, 9 May)
• Re: [w3c/browser-payment-api] editorial: s/web page/developers and s/the developer/developers (#527) (Tuesday, 9 May)

Ezzzydoesit

• [w3c/webpayments-payment-handler] let 's App Pay (#148) (Friday, 5 May)

gogerald

• Re: [w3c/payment-handler] Missing question mark, (#163) (Thursday, 25 May)
• [w3c/payment-handler] Missing question mark, (#163) (Thursday, 25 May)

ianbjacobs

• Re: [w3c/payment-handler] Dead link in an example (#166) (Wednesday, 31 May)
• Re: [w3c/payment-handler] Dead link in an example (#166) (Wednesday, 31 May)
• Re: [w3c/payment-handler] chore(.pr-preview): enable pull request previews (#164) (Wednesday, 31 May)
• Re: [w3c/payment-handler] chore: tidy up (#165) (Wednesday, 31 May)
• Re: [w3c/payment-handler] Missing question mark, (#163) (Wednesday, 31 May)
• Re: [w3c/payment-handler] Missing question mark, (#163) (Tuesday, 30 May)
• Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157) (Thursday, 25 May)
• Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157) (Thursday, 25 May)
• Re: [w3c/webpayments-methods-tokenization] Wiki review (#7) (Thursday, 25 May)
• Re: [w3c/webpayments-methods-tokenization] Wiki review (#7) (Thursday, 25 May)
• Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157) (Wednesday, 24 May)
• Re: [w3c/payment-handler] Support for Abort() being delegated to Payment Handler (#117) (Wednesday, 24 May)
• Re: [w3c/payment-handler] Added "github" param for respec (#161) (Tuesday, 16 May)
• Re: [w3c/webpayments-methods-tokenization] Opportunities (#6) (Tuesday, 16 May)
• Re: [w3c/webpayments-methods-tokenization] Opportunities (#6) (Tuesday, 16 May)
• [w3c/payment-handler] Added "github" param for respec (#161) (Tuesday, 16 May)
• Re: [w3c/webpayments-methods-tokenization] Opportunities (#6) (Monday, 15 May)
• Re: [w3c/webpayments-methods-tokenization] Wording of tokens used (#5) (Monday, 15 May)
• Re: [w3c/payment-handler] Link fixes (#160) (Monday, 15 May)
• Re: [w3c/payment-handler] Link fixes (#160) (Monday, 15 May)
• [w3c/payment-handler] Link fixes (#160) (Monday, 15 May)
• Re: [w3c/payment-handler] link fixes (#159) (Monday, 15 May)
• Re: [w3c/payment-handler] link fixes (#159) (Monday, 15 May)
• Re: [w3c/payment-handler] link fixes (#159) (Monday, 15 May)
• [w3c/payment-handler] link fixes (#159) (Monday, 15 May)
• Re: [w3c/payment-handler] Link fixes (#158) (Monday, 15 May)
• Re: [w3c/payment-handler] Link fixes (#158) (Monday, 15 May)
• [w3c/payment-handler] Link fixes (#158) (Monday, 15 May)
• [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157) (Friday, 12 May)
• Re: [w3c/payment-handler] Establish Editorial process (#156) (Friday, 12 May)
• Re: [w3c/payment-handler] Pre FPWD tweaks (#155) (Thursday, 11 May)
• Re: [w3c/payment-handler] Update README.md (#154) (Thursday, 11 May)
• [w3c/payment-handler] Pre FPWD tweaks (#155) (Thursday, 11 May)
• Re: [w3c/payment-handler] docs(README): reflect recent name change (#152) (Thursday, 11 May)
• Re: [w3c/payment-handler] docs(README): reflect recent name change (#152) (Thursday, 11 May)
• [w3c/payment-handler] Update README.md (#154) (Thursday, 11 May)
• Re: [w3c/browser-payment-api] Add extension point (#492) (Thursday, 11 May)
• Re: [w3c/browser-payment-api] Remove merchant preference language (#518) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] Remove merchant preference language (#518) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] Remove merchant preference language (#518) (Wednesday, 10 May)
• Re: [w3c/webpayments-payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Wednesday, 10 May)
• [w3c/webpayments-methods-tokenization] Replace usage of 'last4' with 'suffix' (#4) (Tuesday, 9 May)
• Re: [w3c/webpayments-methods-tokenization] Add missing images from spec proposal (#1) (Tuesday, 9 May)
• Re: [w3c/webpayments-methods-tokenization] Add missing images from spec proposal (#1) (Tuesday, 9 May)
• Re: [w3c/webpayments-methods-tokenization] Add missing images from spec proposal (#1) (Tuesday, 9 May)
• Re: [w3c/webpayments-payment-handler] Add .clear() to map-likes (#129) (Tuesday, 9 May)
• Re: [w3c/webpayments-payment-handler] editorial: fix references + don't show mailing list details (#150) (Tuesday, 9 May)
• Re: [w3c/webpayments-payment-handler] editorial: make shortname... shorter. (#149) (Tuesday, 9 May)
• Re: [w3c/webpayments-payment-handler] Spec still talks about "payment app" (#151) (Tuesday, 9 May)
• Re: [w3c/webpayments-payment-handler] Add .clear() to map-likes (#129) (Monday, 8 May)
• Re: [w3c/webpayments-payment-handler] let 's App Pay (#148) (Friday, 5 May)
• Re: [w3c/webpayments-payment-handler] Update LICENSE.md (#146) (Thursday, 4 May)
• Re: [w3c/webpayments-payment-handler] Fix wrt group charter (#147) (Thursday, 4 May)
• [w3c/webpayments-payment-handler] Fix wrt group charter (#147) (Thursday, 4 May)
• [w3c/webpayments-payment-handler] Update LICENSE.md (#146) (Thursday, 4 May)
• Re: [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523) (Wednesday, 3 May)
• Re: [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523) (Wednesday, 3 May)
• Re: [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143) (Wednesday, 3 May)
• Re: [w3c/browser-payment-api] editorial: mark currencySystem at risk (#522) (Wednesday, 3 May)
• Re: [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143) (Wednesday, 3 May)
• Re: [w3c/webpayments-payment-handler] Fix to prevent duplicate ids by respec (#145) (Wednesday, 3 May)
• Re: [w3c/webpayments-payment-handler] Fix to prevent duplicate ids by respec (#145) (Wednesday, 3 May)
• Re: [w3c/webpayments-methods-tokenization] Difference between "issuer token" ans "gateway token" (#3) (Wednesday, 3 May)
• Re: [w3c/webpayments-payment-handler] Display may be subject to user and local policy (consider UA making security decisions etc) (#5) (Tuesday, 2 May)
• Re: [w3c/webpayments-payment-handler] Display may be subject to user and local policy (consider UA making security decisions etc) (#5) (Tuesday, 2 May)
• [w3c/webpayments-payment-handler] Fix to prevent duplicate ids by respec (#145) (Tuesday, 2 May)
• Re: [w3c/webpayments-payment-handler] Merge PaymentAppResponse and PaymentRequestEvent (#142) (Tuesday, 2 May)
• Re: [w3c/webpayments-payment-handler] Merge PaymentAppResponse and PaymentRequestEvent (#142) (Tuesday, 2 May)
• Re: [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143) (Tuesday, 2 May)
• Re: [w3c/webpayments-methods-tokenization] Difference between "issuer token" ans "gateway token" (#3) (Tuesday, 2 May)
• Re: [w3c/webpayments-payment-handler] Merge PaymentAppRequest and PaymentRequestEvent (#144) (Tuesday, 2 May)
• [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143) (Tuesday, 2 May)
• Re: [w3c/webpayments-methods-tokenization] Add missing images from spec proposal (#1) (Monday, 1 May)
• Re: [w3c/webpayments-methods-card] Clarify this specification is intended to become a W3C Note (#27) (Monday, 1 May)
• Re: [w3c/webpayments-methods-tokenization] Split up card-token payment method into multiple types (#2) (Monday, 1 May)

Jinho Bang

• Re: [w3c/payment-handler] Missing question mark, (#163) (Wednesday, 31 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Wednesday, 31 May)
• Re: [w3c/payment-handler] Missing question mark, (#163) (Wednesday, 31 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Wednesday, 31 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Wednesday, 31 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Wednesday, 31 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Monday, 29 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Monday, 29 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Sunday, 28 May)
• Re: [w3c/payment-handler] Missing question mark, (#163) (Thursday, 25 May)
• Re: [w3c/payment-handler] Missing question mark, (#163) (Thursday, 25 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Thursday, 25 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Tuesday, 23 May)
• [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Tuesday, 23 May)

ktmitton

• [w3c/browser-payment-api] Shipping Address Validation - Suggest Alternate Address (#537) (Saturday, 27 May)

Manu Sporny

• Re: [w3c/payment-handler] Establish Editorial process (#156) (Friday, 12 May)
• Re: [w3c/webpayments-payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Wednesday, 10 May)
• Re: [w3c/webpayments-payment-handler] Spec still talks about "payment app" (#151) (Tuesday, 9 May)
• Re: [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143) (Wednesday, 3 May)

Marcos Cáceres

• [w3c/browser-payment-api] Make text about CR phase into a note (#542) (Wednesday, 31 May)
• Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Wednesday, 31 May)
• Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512) (Wednesday, 31 May)
• Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512) (Wednesday, 31 May)
• Re: [w3c/payment-handler] chore(.pr-preview): enable pull request previews (#164) (Wednesday, 31 May)
• Re: [w3c/payment-handler] chore: tidy up (#165) (Wednesday, 31 May)
• Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540) (Wednesday, 31 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Wednesday, 31 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Wednesday, 31 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Wednesday, 31 May)
• Re: [w3c/payment-handler] chore: tidy up (#165) (Wednesday, 31 May)
• Re: [w3c/payment-handler] chore(.pr-preview): enable pull request previews (#164) (Wednesday, 31 May)
• [w3c/payment-handler] chore: tidy up (#165) (Wednesday, 31 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Wednesday, 31 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Wednesday, 31 May)
• Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540) (Tuesday, 30 May)
• Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540) (Tuesday, 30 May)
• Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540) (Tuesday, 30 May)
• Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540) (Tuesday, 30 May)
• Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540) (Tuesday, 30 May)
• Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540) (Tuesday, 30 May)
• Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540) (Tuesday, 30 May)
• Re: [w3c/browser-payment-api] Use first matching PaymentDetailsModifier (closes #309) (#541) (Monday, 29 May)
• [w3c/browser-payment-api] Use first matching PaymentDetailsModifier (closes #309) (#541) (Monday, 29 May)
• [w3c/browser-payment-api] Cater for platform-specific limitations (#540) (Monday, 29 May)
• Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23) (Monday, 29 May)
• Re: [w3c/browser-payment-api] Shipping Address Validation - Suggest Alternate Address (#537) (Monday, 29 May)
• [w3c/browser-payment-api] Show better examples of how to deal with change events (#539) (Monday, 29 May)
• [w3c/browser-payment-api] Descriptions of change events attributes are somewhat misleading (#538) (Monday, 29 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Monday, 29 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Monday, 29 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Monday, 29 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Monday, 29 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Monday, 29 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Friday, 26 May)
• [w3c/payment-handler] chore(.pr-preview): enable pull request previews (#164) (Friday, 26 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536) (Thursday, 25 May)
• Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23) (Thursday, 25 May)
• Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162) (Wednesday, 24 May)
• Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23) (Wednesday, 24 May)
• Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23) (Wednesday, 24 May)
• [w3c/browser-payment-api] canMakePayment() needs to match .show() (#535) (Wednesday, 24 May)
• Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23) (Wednesday, 24 May)
• Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23) (Wednesday, 24 May)
• Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23) (Wednesday, 24 May)
• [w3c/browser-payment-api] shippingOption description is misleading (#534) (Tuesday, 23 May)
• Re: [w3c/browser-payment-api] editorial: cleanup of updateWith() (#533) (Tuesday, 23 May)
• Re: [w3c/browser-payment-api] editorial: cleanup of updateWith() (#533) (Monday, 22 May)
• Re: [w3c/browser-payment-api] editorial: cleanup of updateWith() (#533) (Monday, 22 May)
• Re: [w3c/browser-payment-api] editorial: cleanup of updateWith() (#533) (Monday, 22 May)
• [w3c/browser-payment-api] editorial: cleanup of updateWith() (#533) (Monday, 22 May)
• Re: [w3c/browser-payment-api] editorial: destructure tuple (closes #498) (#530) (Monday, 15 May)
• Re: [w3c/browser-payment-api] editorial: destructure tuple (closes #498) (#530) (Monday, 15 May)
• Re: [w3c/browser-payment-api] Consider adding examples of payment matching algorithm (#498) (Monday, 15 May)
• Re: [w3c/browser-payment-api] Ambiguity in "Process payment methods:" (#458) (Monday, 15 May)
• Re: [w3c/browser-payment-api] editorial: rephrase parse, rethrow, or null otherwise (closes #458) (#531) (Monday, 15 May)
• Re: [w3c/browser-payment-api] DOMStrings don't contain "characters" (#322) (Monday, 15 May)
• Re: [w3c/browser-payment-api] editorial: s/characters/code points (closes #322) (#528) (Monday, 15 May)
• Re: [w3c/browser-payment-api] Editorial: paymentResponse.complete() should return a rejected promise, not throw (#509) (Monday, 15 May)
• Re: [w3c/browser-payment-api] editorial: s/throw/reject in complete() (closes #509) (#529) (Monday, 15 May)
• Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512) (Monday, 15 May)
• Re: [w3c/browser-payment-api] PaymentAddress and null values (#495) (Monday, 15 May)
• Re: [w3c/browser-payment-api] PaymentAddress and null values (#495) (Monday, 15 May)
• Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) (Monday, 15 May)
• Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) (Monday, 15 May)
• Re: [w3c/browser-payment-api] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Monday, 15 May)
• [w3c/browser-payment-api] editorial: rephrase 'Process payment methods' (closes #458) (#531) (Monday, 15 May)
• Re: [w3c/browser-payment-api] Consider adding examples of payment matching algorithm (#498) (Monday, 15 May)
• [w3c/browser-payment-api] editorial: destructure tuple (closes #498) (#530) (Monday, 15 May)
• Re: [w3c/browser-payment-api] Reference to payment apps in Introduction needs updating (#496) (Monday, 15 May)
• Re: [w3c/browser-payment-api] Reference to payment apps in Introduction needs updating (#496) (Monday, 15 May)
• [w3c/browser-payment-api] editorial: s/throw/reject in complete() (closes #509) (#529) (Monday, 15 May)
• Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521) (Monday, 15 May)
• Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521) (Monday, 15 May)
• Re: [w3c/browser-payment-api] Consider removing merchant preference language (#481) (Monday, 15 May)
• Re: [w3c/browser-payment-api] Consider removing merchant preference language (#481) (Monday, 15 May)
• [w3c/browser-payment-api] editorial: s/characters/code points (closes #322) (#528) (Monday, 15 May)
• Re: [w3c/payment-handler] Establish Editorial process (#156) (Friday, 12 May)
• Re: [w3c/payment-handler] Establish Editorial process (#156) (Friday, 12 May)
• [w3c/payment-handler] Establish Editorial process (#156) (Friday, 12 May)
• Re: [w3c/browser-payment-api] Add extension point (#492) (Thursday, 11 May)
• Re: [w3c/browser-payment-api] Add extension point (#492) (Thursday, 11 May)
• Re: [w3c/browser-payment-api] Add extension point (#492) (Thursday, 11 May)
• Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512) (Thursday, 11 May)
• Re: [w3c/browser-payment-api] editorial: s/web page/developers (#527) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] Web page and developer (#437) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] editorial: s/web page/developers (#527) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] Remove merchant preference language (#518) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] Remove merchant preference language (#518) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] mark currencySystem as feature at risk (#482) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] mark currencySystem as feature at risk (#482) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] Section for A11Y Considerations (#450) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] Section for A11Y Considerations (#450) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] editorial: consider removing merchant preference language (#518) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] Add extension point (#492) (Wednesday, 10 May)
• Re: [w3c/webpayments-payment-handler] Add .clear() to map-likes (#129) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] editorial: s/web page/developers (#527) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] editorial: s/web page/developers (#527) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] editorial: s/web page/developers (#527) (Wednesday, 10 May)
• Re: [w3c/webpayments-payment-handler] editorial: make shortname... shorter. (#149) (Tuesday, 9 May)
• Re: [w3c/webpayments-payment-handler] editorial: fix references + don't show mailing list details (#150) (Tuesday, 9 May)
• Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521) (Tuesday, 9 May)
• Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521) (Tuesday, 9 May)
• Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521) (Tuesday, 9 May)
• Re: [w3c/webpayments-payment-handler] Spec still talks about "payment app" (#151) (Tuesday, 9 May)
• Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521) (Tuesday, 9 May)
• Re: [w3c/browser-payment-api] editorial: s/web page/developers and s/the developer/developers (#527) (Tuesday, 9 May)
• Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521) (Tuesday, 9 May)
• Re: [w3c/webpayments-payment-handler] Add .clear() to map-likes (#129) (Tuesday, 9 May)
• [w3c/webpayments-payment-handler] docs(README): reflect recent name change (#152) (Tuesday, 9 May)
• [w3c/webpayments-payment-handler] Spec still talks about "payment app" (#151) (Tuesday, 9 May)
• [w3c/webpayments-payment-handler] editorial: fix references + don't show mailing list details (#150) (Tuesday, 9 May)
• [w3c/webpayments-payment-handler] Editorial: make shortname... shorter. (#149) (Tuesday, 9 May)
• Re: [w3c/browser-payment-api] editorial: fix reference to WebIDL spec (#524) (Tuesday, 9 May)
• Re: [w3c/browser-payment-api] editorial: s/payment app/payment handler (#525) (Tuesday, 9 May)
• Re: [w3c/browser-payment-api] Payment App or Payment Handler language (#497) (Tuesday, 9 May)
• Re: [w3c/browser-payment-api] Is PaymentResponse.details the result of a JSON.parse() (#526) (Monday, 8 May)
• Re: [w3c/browser-payment-api] Is PaymentResponse.details the result of a JSON.parse() (#526) (Monday, 8 May)
• Re: [w3c/browser-payment-api] editorial: s/payment app/payment handler (#525) (Monday, 8 May)
• Re: [w3c/browser-payment-api] editorial: s/payment app/payment handler (#525) (Monday, 8 May)
• Re: [w3c/browser-payment-api] editorial: mark currencySystem at risk (#522) (Friday, 5 May)
• Re: [w3c/browser-payment-api] editorial: mark currencySystem at risk (#522) (Friday, 5 May)
• Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 5 May)
• Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512) (Friday, 5 May)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Friday, 5 May)
• Re: [w3c/browser-payment-api] editorial: consider removing merchant preference language (#518) (Thursday, 4 May)
• [w3c/browser-payment-api] editorial: fix reference to WebIDL spec (#524) (Thursday, 4 May)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Thursday, 4 May)
• Re: [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523) (Thursday, 4 May)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Thursday, 4 May)
• Re: [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523) (Wednesday, 3 May)
• Re: [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523) (Wednesday, 3 May)
• [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523) (Wednesday, 3 May)
• Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521) (Wednesday, 3 May)
• Re: [w3c/webpayments-payment-handler] Fix to prevent duplicate ids by respec (#145) (Wednesday, 3 May)
• Re: [w3c/browser-payment-api] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Wednesday, 3 May)
• Re: [w3c/browser-payment-api] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Wednesday, 3 May)
• [w3c/browser-payment-api] editorial: mark currencySystem at risk (#522) (Wednesday, 3 May)
• [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521) (Wednesday, 3 May)
• [w3c/browser-payment-api] CR check list (#520) (Wednesday, 3 May)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Tuesday, 2 May)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Tuesday, 2 May)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Tuesday, 2 May)
• Re: [w3c/webpayments-methods-card] Clarify this specification is intended to become a W3C Note (#27) (Monday, 1 May)
• [w3c/browser-payment-api] editorial: add link to test suite (#519) (Monday, 1 May)
• Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Monday, 1 May)

MasterKeyur

• Re: [w3c/webpayments-methods-tokenization] Opportunities (#6) (Tuesday, 16 May)
• [w3c/webpayments-methods-tokenization] Opportunities (#6) (Friday, 12 May)
• [w3c/webpayments-methods-tokenization] Wording of tokens used (#5) (Friday, 12 May)

mattsaxon

• Re: [w3c/browser-payment-api] Consider adding examples of payment matching algorithm (#498) (Tuesday, 16 May)
• Re: [w3c/browser-payment-api] Remove merchant preference language (#518) (Thursday, 11 May)
• Re: [w3c/browser-payment-api] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Wednesday, 3 May)
• Re: [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143) (Wednesday, 3 May)
• Re: [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143) (Tuesday, 2 May)

Michael[tm] Smith

• Re: [w3c/payment-handler] Link fixes (#158) (Monday, 15 May)

nelsonlyra

• [w3c/webpayments-methods-tokenization] Wiki review (#7) (Tuesday, 23 May)
• Re: [w3c/webpayments-methods-tokenization] Difference between "issuer token" ans "gateway token" (#3) (Wednesday, 3 May)
• [w3c/webpayments-methods-tokenization] Difference between "issuer token" ans "gateway token" (#3) (Tuesday, 2 May)

Olivier Yiptong

• Re: [w3c/webpayments-methods-tokenization] Split up card-token payment method into multiple types (#2) (Tuesday, 2 May)
• Re: [w3c/webpayments-methods-tokenization] Split up card-token payment method into multiple types (#2) (Tuesday, 2 May)
• Re: [w3c/webpayments-methods-tokenization] Split up card-token payment method into multiple types (#2) (Tuesday, 2 May)
• [w3c/webpayments-methods-tokenization] Split up card-token payment method into multiple types (#2) (Monday, 1 May)
• Re: [w3c/webpayments-methods-tokenization] Add missing images from spec proposal (#1) (Monday, 1 May)
• [w3c/webpayments-methods-tokenization] Add missing images from spec proposal (#1) (Monday, 1 May)

Philip Jägenstedt

• Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540) (Monday, 29 May)
• Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540) (Monday, 29 May)

Rouslan Solomakhin

• Re: [w3c/payment-handler] Missing question mark, (#163) (Wednesday, 31 May)
• Re: [w3c/payment-handler] Missing question mark, (#163) (Thursday, 25 May)
• Re: [w3c/payment-handler] Missing question mark, (#163) (Thursday, 25 May)
• Re: [w3c/payment-handler] Missing question mark, (#163) (Thursday, 25 May)
• Re: [w3c/payment-handler] Missing question mark, (#163) (Thursday, 25 May)
• Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157) (Thursday, 25 May)
• Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157) (Wednesday, 24 May)
• Re: [w3c/payment-handler] Support for Abort() being delegated to Payment Handler (#117) (Wednesday, 24 May)
• Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157) (Wednesday, 24 May)
• Re: [w3c/payment-handler] Establish Editorial process (#156) (Friday, 12 May)

Simon Pieters

• Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540) (Tuesday, 30 May)
• Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540) (Tuesday, 30 May)
• Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540) (Tuesday, 30 May)
• Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540) (Tuesday, 30 May)
• Re: [w3c/browser-payment-api] editorial: fix reference to WebIDL spec (#524) (Friday, 5 May)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Thursday, 4 May)

Takeshi Yoshino

• Re: [w3c/payment-handler] Dead link in an example (#166) (Wednesday, 31 May)
• [w3c/payment-handler] Dead link in an example (#166) (Wednesday, 31 May)

Tobie Langel

• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Thursday, 4 May)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Thursday, 4 May)

Zach Koch

• Re: [w3c/browser-payment-api] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Wednesday, 24 May)
• Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23) (Wednesday, 24 May)
• Re: [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] editorial: mark currencySystem at risk (#522) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] editorial: add link to test suite (#519) (Wednesday, 10 May)
• Re: [w3c/browser-payment-api] remove merchant preference language (#518) (Wednesday, 10 May)

Last message date: Wednesday, 31 May 2017 22:38:48 UTC