Wednesday, 31 May 2017
- [w3c/browser-payment-api] Make text about CR phase into a note (#542)
- Re: [w3c/browser-payment-api] should .show() be user gated? (#486)
- Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512)
- Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512)
- Re: [w3c/payment-handler] Missing question mark, (#163)
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
- Re: [w3c/payment-handler] Missing question mark, (#163)
- Re: [w3c/payment-handler] chore(.pr-preview): enable pull request previews (#164)
- Re: [w3c/payment-handler] chore: tidy up (#165)
- Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540)
- Re: [w3c/payment-handler] Dead link in an example (#166)
- Re: [w3c/payment-handler] Dead link in an example (#166)
- Re: [w3c/payment-handler] Dead link in an example (#166)
- [w3c/payment-handler] Dead link in an example (#166)
- Re: [w3c/payment-handler] chore(.pr-preview): enable pull request previews (#164)
- Re: [w3c/payment-handler] chore: tidy up (#165)
- Re: [w3c/payment-handler] Missing question mark, (#163)
- Re: [w3c/payment-handler] Missing question mark, (#163)
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
- Re: [w3c/payment-handler] chore: tidy up (#165)
- Re: [w3c/payment-handler] chore(.pr-preview): enable pull request previews (#164)
- [w3c/payment-handler] chore: tidy up (#165)
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
Tuesday, 30 May 2017
- Re: [w3c/payment-handler] Missing question mark, (#163)
- Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540)
- Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540)
- Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540)
- Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540)
- Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540)
- Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540)
- Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540)
- Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540)
- Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540)
- Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540)
- Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540)
Monday, 29 May 2017
- Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540)
- Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540)
- Re: [w3c/browser-payment-api] Cater for platform-specific limitations (#540)
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
- Re: [w3c/browser-payment-api] Use first matching PaymentDetailsModifier (closes #309) (#541)
- [w3c/browser-payment-api] Use first matching PaymentDetailsModifier (closes #309) (#541)
- [w3c/browser-payment-api] Cater for platform-specific limitations (#540)
- Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23)
- Re: [w3c/browser-payment-api] Shipping Address Validation - Suggest Alternate Address (#537)
- [w3c/browser-payment-api] Show better examples of how to deal with change events (#539)
- [w3c/browser-payment-api] Descriptions of change events attributes are somewhat misleading (#538)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
Sunday, 28 May 2017
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
Saturday, 27 May 2017
Friday, 26 May 2017
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- [w3c/payment-handler] chore(.pr-preview): enable pull request previews (#164)
- Re: [w3c/browser-payment-api] shippingOption description is misleading (#534)
Thursday, 25 May 2017
- Re: [w3c/payment-handler] Missing question mark, (#163)
- Re: [w3c/payment-handler] Missing question mark, (#163)
- Re: [w3c/payment-handler] Missing question mark, (#163)
- Re: [w3c/payment-handler] Missing question mark, (#163)
- Re: [w3c/payment-handler] Missing question mark, (#163)
- Re: [w3c/payment-handler] Missing question mark, (#163)
- Re: [w3c/payment-handler] Missing question mark, (#163)
- [w3c/payment-handler] Missing question mark, (#163)
- Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157)
- Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157)
- Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/webpayments-methods-tokenization] Wiki review (#7)
- Re: [w3c/webpayments-methods-tokenization] Wiki review (#7)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- [w3c/browser-payment-api] editorial: clarify that payment handler data is converted (#536)
- Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23)
Wednesday, 24 May 2017
- Re: [w3c/browser-payment-api] Add payerGivenName + payerFamilyName to PaymentAddress (#480)
- Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23)
- Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157)
- Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157)
- Re: [w3c/payment-handler] Support for Abort() being delegated to Payment Handler (#117)
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
- Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23)
- Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23)
- [w3c/browser-payment-api] canMakePayment() needs to match .show() (#535)
- Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23)
- Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23)
- Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23)
- Re: [w3c/payment-handler] Support for Abort() being delegated to Payment Handler (#117)
- Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157)
Tuesday, 23 May 2017
- Re: [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
- [w3c/payment-handler] Add a constructor of PaymentRequestEvent and PaymentRequestEventInit. (#162)
- [w3c/webpayments-methods-tokenization] Wiki review (#7)
- [w3c/browser-payment-api] shippingOption description is misleading (#534)
- Re: [w3c/browser-payment-api] editorial: cleanup of updateWith() (#533)
- Re: [w3c/browser-payment-api] editorial: cleanup of updateWith() (#533)
Monday, 22 May 2017
- Re: [w3c/browser-payment-api] editorial: cleanup of updateWith() (#533)
- Re: [w3c/browser-payment-api] editorial: cleanup of updateWith() (#533)
- Re: [w3c/browser-payment-api] editorial: cleanup of updateWith() (#533)
- Re: [w3c/browser-payment-api] editorial: cleanup of updateWith() (#533)
- [w3c/browser-payment-api] editorial: cleanup of updateWith() (#533)
Tuesday, 16 May 2017
- Re: [w3c/payment-handler] Added "github" param for respec (#161)
- Re: [w3c/webpayments-methods-tokenization] Opportunities (#6)
- Re: [w3c/webpayments-methods-tokenization] Opportunities (#6)
- Re: [w3c/webpayments-methods-tokenization] Opportunities (#6)
- Re: [w3c/payment-handler] Added "github" param for respec (#161)
- [w3c/payment-handler] Added "github" param for respec (#161)
- Re: [w3c/browser-payment-api] editorial: destructure tuple (closes #498) (#530)
- [w3c/browser-payment-api] Matching algo doesn't handle (#532)
- Re: [w3c/browser-payment-api] Consider adding examples of payment matching algorithm (#498)
Monday, 15 May 2017
- Re: [w3c/browser-payment-api] editorial: destructure tuple (closes #498) (#530)
- Re: [w3c/browser-payment-api] editorial: destructure tuple (closes #498) (#530)
- Re: [w3c/browser-payment-api] Consider adding examples of payment matching algorithm (#498)
- Re: [w3c/browser-payment-api] Ambiguity in "Process payment methods:" (#458)
- Re: [w3c/browser-payment-api] editorial: rephrase parse, rethrow, or null otherwise (closes #458) (#531)
- Re: [w3c/browser-payment-api] DOMStrings don't contain "characters" (#322)
- Re: [w3c/browser-payment-api] editorial: s/characters/code points (closes #322) (#528)
- Re: [w3c/browser-payment-api] Editorial: paymentResponse.complete() should return a rejected promise, not throw (#509)
- Re: [w3c/browser-payment-api] editorial: s/throw/reject in complete() (closes #509) (#529)
- Re: [w3c/browser-payment-api] editorial: s/throw/reject in complete() (closes #509) (#529)
- Re: [w3c/browser-payment-api] editorial: s/characters/code points (closes #322) (#528)
- Re: [w3c/browser-payment-api] editorial: rephrase parse, rethrow, or null otherwise (closes #458) (#531)
- Re: [w3c/browser-payment-api] editorial: destructure tuple (closes #498) (#530)
- Re: [w3c/webpayments-methods-tokenization] Opportunities (#6)
- Re: [w3c/webpayments-methods-tokenization] Wording of tokens used (#5)
- Re: [w3c/payment-handler] Link fixes (#160)
- Re: [w3c/payment-handler] Link fixes (#160)
- Re: [w3c/payment-handler] Link fixes (#160)
- [w3c/payment-handler] Link fixes (#160)
- Re: [w3c/payment-handler] link fixes (#159)
- Re: [w3c/payment-handler] link fixes (#159)
- Re: [w3c/payment-handler] link fixes (#159)
- Re: [w3c/payment-handler] link fixes (#159)
- [w3c/payment-handler] link fixes (#159)
- Re: [w3c/payment-handler] Link fixes (#158)
- Re: [w3c/payment-handler] Link fixes (#158)
- Re: [w3c/payment-handler] Link fixes (#158)
- [w3c/payment-handler] Link fixes (#158)
- Re: [w3c/browser-payment-api] editorial: destructure tuple (closes #498) (#530)
- Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512)
- Re: [w3c/browser-payment-api] PaymentAddress and null values (#495)
- Re: [w3c/browser-payment-api] PaymentAddress and null values (#495)
- Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493)
- Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493)
- Re: [w3c/browser-payment-api] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476)
- [w3c/browser-payment-api] editorial: rephrase 'Process payment methods' (closes #458) (#531)
- Re: [w3c/browser-payment-api] Consider adding examples of payment matching algorithm (#498)
- [w3c/browser-payment-api] editorial: destructure tuple (closes #498) (#530)
- Re: [w3c/browser-payment-api] Reference to payment apps in Introduction needs updating (#496)
- Re: [w3c/browser-payment-api] Reference to payment apps in Introduction needs updating (#496)
- [w3c/browser-payment-api] editorial: s/throw/reject in complete() (closes #509) (#529)
- Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521)
- Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521)
- Re: [w3c/browser-payment-api] Consider removing merchant preference language (#481)
- Re: [w3c/browser-payment-api] Consider removing merchant preference language (#481)
- [w3c/browser-payment-api] editorial: s/characters/code points (closes #322) (#528)
Friday, 12 May 2017
- [w3c/webpayments-methods-tokenization] Opportunities (#6)
- [w3c/webpayments-methods-tokenization] Wording of tokens used (#5)
- [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157)
- Re: [w3c/payment-handler] Establish Editorial process (#156)
- Re: [w3c/payment-handler] Establish Editorial process (#156)
- Re: [w3c/payment-handler] Establish Editorial process (#156)
- Re: [w3c/payment-handler] Establish Editorial process (#156)
- Re: [w3c/payment-handler] Establish Editorial process (#156)
- Re: [w3c/payment-handler] Establish Editorial process (#156)
- Re: [w3c/payment-handler] Establish Editorial process (#156)
- [w3c/payment-handler] Establish Editorial process (#156)
Thursday, 11 May 2017
- Re: [w3c/payment-handler] Pre FPWD tweaks (#155)
- Re: [w3c/payment-handler] Update README.md (#154)
- Re: [w3c/browser-payment-api] Remove merchant preference language (#518)
- Re: [w3c/payment-handler] Pre FPWD tweaks (#155)
- Re: [w3c/payment-handler] Update README.md (#154)
- [w3c/payment-handler] Pre FPWD tweaks (#155)
- Re: [w3c/payment-handler] docs(README): reflect recent name change (#152)
- Re: [w3c/payment-handler] docs(README): reflect recent name change (#152)
- [w3c/payment-handler] Update README.md (#154)
- Re: [w3c/browser-payment-api] Add extension point (#492)
- Re: [w3c/browser-payment-api] Add extension point (#492)
- Re: [w3c/browser-payment-api] Add explicit extension point to matching algo (#470)
- Re: [w3c/browser-payment-api] Add extension point (#492)
- Re: [w3c/browser-payment-api] Add extension point (#492)
- Re: [w3c/browser-payment-api] Add extension point (#492)
- Re: [w3c/browser-payment-api] Add extension point (#492)
- Re: [w3c/browser-payment-api] Add extension point (#492)
- Re: [w3c/browser-payment-api] Add extension point (#492)
- Re: [w3c/browser-payment-api] Add extension point (#492)
- Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512)
Wednesday, 10 May 2017
- Re: [w3c/browser-payment-api] editorial: s/web page/developers (#527)
- Re: [w3c/browser-payment-api] Web page and developer (#437)
- Re: [w3c/browser-payment-api] editorial: s/web page/developers (#527)
- Re: [w3c/browser-payment-api] Remove merchant preference language (#518)
- Re: [w3c/browser-payment-api] Remove merchant preference language (#518)
- Re: [w3c/browser-payment-api] Remove merchant preference language (#518)
- Re: [w3c/browser-payment-api] Remove merchant preference language (#518)
- Re: [w3c/browser-payment-api] Remove merchant preference language (#518)
- Re: [w3c/browser-payment-api] mark currencySystem as feature at risk (#482)
- Re: [w3c/browser-payment-api] mark currencySystem as feature at risk (#482)
- Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512)
- Re: [w3c/browser-payment-api] Section for A11Y Considerations (#450)
- Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512)
- Re: [w3c/browser-payment-api] Section for A11Y Considerations (#450)
- Re: [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523)
- Re: [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523)
- Re: [w3c/browser-payment-api] editorial: mark currencySystem at risk (#522)
- Re: [w3c/browser-payment-api] editorial: mark currencySystem at risk (#522)
- Re: [w3c/browser-payment-api] editorial: add link to test suite (#519)
- Re: [w3c/browser-payment-api] editorial: add link to test suite (#519)
- Re: [w3c/browser-payment-api] remove merchant preference language (#518)
- Re: [w3c/browser-payment-api] editorial: consider removing merchant preference language (#518)
- Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512)
- Re: [w3c/browser-payment-api] Add extension point (#492)
- Re: [w3c/browser-payment-api] Add extension point (#492)
- Re: [w3c/webpayments-payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153)
- Re: [w3c/webpayments-payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153)
- Re: [w3c/webpayments-payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153)
- Re: [w3c/webpayments-payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153)
- Re: [w3c/webpayments-payment-handler] Add .clear() to map-likes (#129)
- Re: [w3c/browser-payment-api] editorial: s/web page/developers (#527)
- Re: [w3c/browser-payment-api] editorial: s/web page/developers (#527)
- Re: [w3c/browser-payment-api] editorial: s/web page/developers (#527)
- Re: [w3c/browser-payment-api] editorial: s/web page/developers (#527)
- Re: [w3c/webpayments-payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153)
- [w3c/webpayments-payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153)
Tuesday, 9 May 2017
- Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521)
- [w3c/webpayments-methods-tokenization] Replace usage of 'last4' with 'suffix' (#4)
- Re: [w3c/webpayments-methods-tokenization] Add missing images from spec proposal (#1)
- Re: [w3c/webpayments-methods-tokenization] Add missing images from spec proposal (#1)
- Re: [w3c/webpayments-methods-tokenization] Add missing images from spec proposal (#1)
- Re: [w3c/webpayments-payment-handler] editorial: make shortname... shorter. (#149)
- Re: [w3c/webpayments-payment-handler] editorial: fix references + don't show mailing list details (#150)
- Re: [w3c/webpayments-payment-handler] Spec still talks about "payment app" (#151)
- Re: [w3c/webpayments-payment-handler] Add .clear() to map-likes (#129)
- Re: [w3c/webpayments-payment-handler] editorial: fix references + don't show mailing list details (#150)
- Re: [w3c/webpayments-payment-handler] editorial: make shortname... shorter. (#149)
- Re: [w3c/webpayments-payment-handler] Spec still talks about "payment app" (#151)
- Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521)
- Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521)
- Re: [w3c/webpayments-payment-handler] Spec still talks about "payment app" (#151)
- Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521)
- Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521)
- Re: [w3c/webpayments-payment-handler] Spec still talks about "payment app" (#151)
- Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521)
- Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521)
- Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521)
- Re: [w3c/webpayments-payment-handler] Spec still talks about "payment app" (#151)
- Re: [w3c/browser-payment-api] editorial: s/web page/developers and s/the developer/developers (#527)
- Re: [w3c/browser-payment-api] editorial: s/web page/developers and s/the developer/developers (#527)
- Re: [w3c/browser-payment-api] editorial: s/web page/developers and s/the developer/developers (#527)
- [w3c/browser-payment-api] editorial: s/web page/developers and s/the developer/developers (#527)
- Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521)
- Re: [w3c/webpayments-payment-handler] Add .clear() to map-likes (#129)
- [w3c/webpayments-payment-handler] docs(README): reflect recent name change (#152)
- [w3c/webpayments-payment-handler] Spec still talks about "payment app" (#151)
- [w3c/webpayments-payment-handler] editorial: fix references + don't show mailing list details (#150)
- [w3c/webpayments-payment-handler] Editorial: make shortname... shorter. (#149)
- Re: [w3c/browser-payment-api] editorial: fix reference to WebIDL spec (#524)
- Re: [w3c/browser-payment-api] editorial: s/payment app/payment handler (#525)
- Re: [w3c/browser-payment-api] Payment App or Payment Handler language (#497)
Monday, 8 May 2017
- Re: [w3c/webpayments-payment-handler] Add .clear() to map-likes (#129)
- Re: [w3c/browser-payment-api] Is PaymentResponse.details the result of a JSON.parse() (#526)
- Re: [w3c/browser-payment-api] Is PaymentResponse.details the result of a JSON.parse() (#526)
- [w3c/browser-payment-api] Is PaymentResponse.details the result of a JSON.parse() (#526)
- Re: [w3c/browser-payment-api] editorial: s/payment app/payment handler (#525)
- Re: [w3c/browser-payment-api] editorial: s/payment app/payment handler (#525)
- [w3c/browser-payment-api] editorial: s/payment app/payment handler (#525)
Friday, 5 May 2017
- Re: [w3c/webpayments-payment-handler] let 's App Pay (#148)
- [w3c/webpayments-payment-handler] let 's App Pay (#148)
- Re: [w3c/browser-payment-api] editorial: fix reference to WebIDL spec (#524)
- Re: [w3c/browser-payment-api] editorial: mark currencySystem at risk (#522)
- Re: [w3c/browser-payment-api] editorial: mark currencySystem at risk (#522)
- Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35)
- Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512)
- Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455)
Thursday, 4 May 2017
- Re: [w3c/webpayments-payment-handler] Update LICENSE.md (#146)
- Re: [w3c/webpayments-payment-handler] Fix wrt group charter (#147)
- Re: [w3c/webpayments-payment-handler] Update LICENSE.md (#146)
- Re: [w3c/webpayments-payment-handler] Fix wrt group charter (#147)
- [w3c/webpayments-payment-handler] Fix wrt group charter (#147)
- Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455)
- [w3c/webpayments-payment-handler] Update LICENSE.md (#146)
- Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455)
- Re: [w3c/browser-payment-api] editorial: consider removing merchant preference language (#518)
- [w3c/browser-payment-api] editorial: fix reference to WebIDL spec (#524)
- Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455)
- Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455)
- Re: [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523)
- Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455)
Wednesday, 3 May 2017
- Re: [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523)
- Re: [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523)
- Re: [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523)
- Re: [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143)
- Re: [w3c/browser-payment-api] editorial: mark currencySystem at risk (#522)
- Re: [w3c/browser-payment-api] editorial: mark currencySystem at risk (#522)
- Re: [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143)
- Re: [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143)
- Re: [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143)
- Re: [w3c/webpayments-payment-handler] Fix to prevent duplicate ids by respec (#145)
- Re: [w3c/webpayments-payment-handler] Fix to prevent duplicate ids by respec (#145)
- Re: [w3c/webpayments-methods-tokenization] Difference between "issuer token" ans "gateway token" (#3)
- Re: [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143)
- Re: [w3c/browser-payment-api] editorial: mark currencySystem at risk (#522)
- Re: [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523)
- Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521)
- Re: [w3c/webpayments-methods-tokenization] Difference between "issuer token" ans "gateway token" (#3)
- Re: [w3c/browser-payment-api] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476)
- Re: [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143)
- Re: [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523)
- [w3c/browser-payment-api] editorial: document mandatory things needed for cr (#523)
- Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521)
- Re: [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521)
- Re: [w3c/webpayments-payment-handler] Fix to prevent duplicate ids by respec (#145)
- Re: [w3c/webpayments-payment-handler] Fix to prevent duplicate ids by respec (#145)
- Re: [w3c/webpayments-payment-handler] Fix to prevent duplicate ids by respec (#145)
- Re: [w3c/browser-payment-api] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476)
- Re: [w3c/browser-payment-api] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476)
- [w3c/browser-payment-api] editorial: mark currencySystem at risk (#522)
- [w3c/browser-payment-api] Change the value of currencySystem to an enum (#521)
- [w3c/browser-payment-api] CR check list (#520)
Tuesday, 2 May 2017
- Re: [w3c/webpayments-payment-handler] Display may be subject to user and local policy (consider UA making security decisions etc) (#5)
- Re: [w3c/webpayments-payment-handler] Display may be subject to user and local policy (consider UA making security decisions etc) (#5)
- [w3c/webpayments-payment-handler] Fix to prevent duplicate ids by respec (#145)
- Re: [w3c/webpayments-payment-handler] Merge PaymentAppResponse and PaymentRequestEvent (#142)
- Re: [w3c/webpayments-payment-handler] Merge PaymentAppResponse and PaymentRequestEvent (#142)
- Re: [w3c/webpayments-payment-handler] Merge PaymentAppRequest and PaymentRequestEvent (#144)
- Re: [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143)
- Re: [w3c/webpayments-methods-tokenization] Difference between "issuer token" ans "gateway token" (#3)
- Re: [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143)
- Re: [w3c/webpayments-methods-tokenization] Split up card-token payment method into multiple types (#2)
- Re: [w3c/webpayments-methods-tokenization] Split up card-token payment method into multiple types (#2)
- Re: [w3c/webpayments-payment-handler] Merge PaymentAppRequest and PaymentRequestEvent (#144)
- Re: [w3c/webpayments-methods-tokenization] Split up card-token payment method into multiple types (#2)
- [w3c/webpayments-payment-handler] Merge PaymentAppRequest and PaymentRequestEvent (#144)
- [w3c/webpayments-payment-handler] How to support communication with a payment app after initial PR API interaction? (#143)
- Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455)
- Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455)
- Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455)
- [w3c/webpayments-methods-tokenization] Difference between "issuer token" ans "gateway token" (#3)
Monday, 1 May 2017
- Re: [w3c/webpayments-methods-tokenization] Add missing images from spec proposal (#1)
- Re: [w3c/webpayments-methods-card] Clarify this specification is intended to become a W3C Note (#27)
- Re: [w3c/webpayments-methods-tokenization] Split up card-token payment method into multiple types (#2)
- [w3c/webpayments-methods-tokenization] Split up card-token payment method into multiple types (#2)
- Re: [w3c/webpayments-methods-tokenization] Add missing images from spec proposal (#1)
- [w3c/webpayments-methods-tokenization] Add missing images from spec proposal (#1)
- Re: [w3c/webpayments-methods-card] Clarify this specification is intended to become a W3C Note (#27)
- [w3c/browser-payment-api] editorial: add link to test suite (#519)
- Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35)