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

adamroach

• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Friday, 28 July)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Friday, 28 July)

Addison Phillips

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

Ade Bateman

• Re: [w3c/browser-payment-api] Editorial changes (#559) (Tuesday, 11 July)

Adrian Hope-Bailie

• Re: [w3c/payment-request] Matching algo doesn't handle absence of filters (#532) (Friday, 28 July)
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) (Wednesday, 26 July)
• Re: [w3c/payment-handler] Chore: Removed duplicate issue 173 (#195) (Wednesday, 26 July)
• Re: [w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36) (Wednesday, 26 July)
• Re: [w3c/payment-request] Drop invalid PMIs in PR ctor (closes #557 #464) (e3893b3) (Tuesday, 25 July)
• Re: [w3c/payment-request] Drop invalid PMIs in PR ctor (closes #557 #464) (e3893b3) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Add missing </section> after #188 PR. (#193) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Add missing </section> after #188 PR. (#193) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Remove wallets, clean up issues (#188) (Monday, 24 July)
• Re: [w3c/payment-handler] Remove wallets, clean up issues (#188) (Monday, 24 July)
• Re: [w3c/payment-handler] Add .clear() to map-likes (#129) (Sunday, 23 July)
• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) (Sunday, 23 July)
• Re: [w3c/payment-handler] Remove wallets, clean up issues (#188) (Friday, 21 July)
• Re: [w3c/payment-handler] Remove wallets, clean up issues (#188) (Friday, 21 July)
• [w3c/payment-handler] Remove wallets, clean up issues (#188) (Friday, 21 July)
• Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173) (Friday, 21 July)
• Re: [w3c/payment-handler] Multiple payment apps per origin (#98) (Friday, 21 July)
• Re: [w3c/payment-handler] Multiple payment apps per origin (#98) (Friday, 21 July)
• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) (Friday, 21 July)
• Re: [w3c/payment-handler] Add .clear() to map-likes (#129) (Friday, 21 July)
• Re: [w3c/payment-handler] Add .clear() to map-likes (#129) (Friday, 21 July)

Anders Rundgren

• [w3c/payment-request] Don't understand how to support outsourced payment providers using CNP + basic card (#566) (Saturday, 29 July)

Ben Tian

• Re: [w3c/browser-payment-api] Editorial: move+rework examples (#553) (Thursday, 20 July)

Denis Ah-Kang

• Re: [w3c/payment-method-id] Auto-publishing failing on bad token (#43) (Monday, 24 July)
• Re: [w3c/payment-method-id] Auto-publishing failing on bad token (#43) (Monday, 24 July)
• Re: [w3c/payment-method-id] Auto-publishing failing on bad token (#43) (Monday, 24 July)

Domenic Denicola

• Re: [w3c/payment-request] chore: rename repo to match shortname (#564) (Wednesday, 26 July)
• Re: [w3c/browser-payment-api] chore: rename repo to match shortname (#564) (Monday, 24 July)

gogerald

• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Friday, 28 July)
• Re: [w3c/payment-handler] The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense (#192) (Thursday, 27 July)

hober

• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Monday, 24 July)

ianbjacobs

• Re: [w3c/payment-request] Don't understand how to support outsourced payment providers using CNP + basic card (#566) (Saturday, 29 July)
• Re: [w3c/payment-request] Don't understand how to support outsourced payment providers using CNP + basic card (#566) (Saturday, 29 July)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Saturday, 29 July)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Friday, 28 July)
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Friday, 28 July)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Friday, 28 July)
• Re: [w3c/payment-request] Add Guidance Text for User Consent (#229) (Friday, 28 July)
• Re: [w3c/payment-request] Add Guidance Text for User Consent (#229) (Friday, 28 July)
• Re: [w3c/payment-handler] Chore: Removed duplicate issue 173 (#195) (Friday, 28 July)
• Re: [w3c/payment-request] chore: rename repo to match shortname (#564) (Wednesday, 26 July)
• Re: [w3c/payment-handler] Chore: Removed duplicate issue 173 (#195) (Wednesday, 26 July)
• [w3c/payment-handler] Chore: Removed duplicate issue 173 (#195) (Wednesday, 26 July)
• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Add missing </section> after #188 PR. (#193) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Remove wallets, clean up issues (#188) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Remove wallets, clean up issues (#188) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189) (Monday, 24 July)
• Re: [w3c/payment-request] chore: rename repo to match shortname (#564) (Monday, 24 July)
• Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189) (Monday, 24 July)
• [w3c/payment-handler] Changed Jason to Andre per their request (#189) (Monday, 24 July)
• Re: [w3c/payment-handler] Add .clear() to map-likes (#129) (Monday, 24 July)
• Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173) (Monday, 24 July)
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) (Monday, 24 July)
• Re: [w3c/browser-payment-api] editorial: fix CR exit date, add exit criteria (#563) (Monday, 24 July)
• [w3c/webpayments-methods-tokenization] Structuring the tokenization payment method(s) (#13) (Friday, 21 July)
• Re: [w3c/payment-handler] Remove wallets, clean up issues (#188) (Friday, 21 July)
• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) (Friday, 21 July)
• Re: [w3c/payment-handler] Add .clear() to map-likes (#129) (Friday, 21 July)
• Re: [w3c/payment-handler] Add .clear() to map-likes (#129) (Friday, 21 July)
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Thursday, 20 July)
• Re: [w3c/payment-method-id] Rename repo payment-method-id (#38) (Wednesday, 19 July)
• [w3c/webpayments-methods-tokenization] Should the response data include an "expires" field? (#12) (Tuesday, 18 July)
• Re: [w3c/payment-handler] How to support communication with a payment app after initial PR API interaction? (#143) (Tuesday, 18 July)
• Re: [w3c/payment-handler] How to support communication with a payment app after initial PR API interaction? (#143) (Tuesday, 18 July)
• Re: [w3c/webpayments-method-identifiers] CR checklist (#39) (Tuesday, 18 July)
• Re: [w3c/browser-payment-api] Use first matching PaymentDetailsModifier (#541) (Tuesday, 18 July)
• Re: [w3c/browser-payment-api] Editorial changes (#559) (Tuesday, 18 July)
• Re: [w3c/browser-payment-api] Editorial changes (#559) (Tuesday, 18 July)
• Re: [w3c/webpayments-method-identifiers] Rename repo payment-method-id (#38) (Tuesday, 18 July)
• Re: [w3c/webpayments-methods-tokenization] Payment Method declaration may show duplicate card descriptions (#9) (Monday, 17 July)
• Re: [w3c/browser-payment-api] Editorial changes (#559) (Monday, 17 July)
• Re: [w3c/browser-payment-api] Editorial changes (#559) (Monday, 17 July)
• Re: [w3c/browser-payment-api] Editorial changes (#559) (Monday, 17 July)
• Re: [w3c/browser-payment-api] Editorial changes (#559) (Monday, 17 July)
• Re: [w3c/browser-payment-api] CR check list (#520) (Monday, 17 July)
• Re: [w3c/browser-payment-api] Editorial changes (#559) (Tuesday, 11 July)
• Re: [w3c/browser-payment-api] CR check list (#520) (Tuesday, 11 July)
• Re: [w3c/browser-payment-api] Editorial changes (#559) (Tuesday, 11 July)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Tuesday, 11 July)
• Re: [w3c/browser-payment-api] Drop array support for supported methods? (#549) (Tuesday, 11 July)
• [w3c/browser-payment-api] Editorial changes (#559) (Monday, 10 July)
• Re: [w3c/browser-payment-api] Drop array support for supported methods? (#549) (Monday, 10 July)
• Re: [w3c/webpayments-methods-tokenization] Wording of tokens used (#5) (Monday, 10 July)
• Re: [w3c/payment-handler] Pictures would help! (#49) (Monday, 10 July)
• Re: [w3c/payment-handler] Pictures would help! (#49) (Monday, 10 July)
• Re: [w3c/payment-handler] Missing question mark, (#163) (Monday, 10 July)
• Re: [w3c/payment-handler] Missing question mark, (#163) (Monday, 10 July)
• Re: [w3c/browser-payment-api] UX guidance article (#558) (Monday, 10 July)
• Re: [w3c/browser-payment-api] Editorial: consider removing merchant preference language (#506) (Monday, 10 July)
• Re: [w3c/payment-handler] PaymentRequestEvent.total should be PaymentCurrencyAmount. (#187) (Saturday, 8 July)

Jinho Bang

• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) (Tuesday, 25 July)
• [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Add missing </section> after #188 PR. (#193) (Tuesday, 25 July)
• [w3c/payment-handler] Add missing </section> after #188 PR. (#193) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Tuesday, 11 July)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Thursday, 6 July)
• Re: [w3c/payment-handler] PaymentRequestEvent.total should be PaymentCurrencyAmount. (#187) (Thursday, 6 July)
• Re: [w3c/payment-handler] PaymentRequestEvent.total should be PaymentCurrencyAmount. (#187) (Thursday, 6 July)
• [w3c/payment-handler] PaymentRequestEvent.total should be PaymentCurrencyAmount. (#187) (Thursday, 6 July)

Marcos Cáceres

• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Monday, 31 July)
• Re: [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Monday, 31 July)
• [w3c/payment-request] validate PaymentCurrencyAmount.currency (closes #490) (#567) (Monday, 31 July)
• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Friday, 28 July)
• Re: [w3c/payment-handler] Chore: Removed duplicate issue 173 (#195) (Friday, 28 July)
• Re: [w3c/payment-handler] Chore: Removed duplicate issue 173 (#195) (Friday, 28 July)
• Re: [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) (Friday, 28 July)
• Re: [w3c/payment-method-basic-card] editorial: cleanup, tidy, ReSpec warns, etc. (#37) (Thursday, 27 July)
• Re: [w3c/payment-method-id] Clarify validation of standardized PMIs (#41) (Wednesday, 26 July)
• Re: [w3c/payment-method-id] Add ignore example (#37) (Wednesday, 26 July)
• Re: [w3c/payment-method-id] Clarify validation of standardized PMIs (#41) (Wednesday, 26 July)
• [w3c/payment-method-basic-card] editorial: cleanup, tidy, ReSpec warns, etc. (#37) (Wednesday, 26 July)
• Re: [w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36) (Wednesday, 26 July)
• Re: [w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36) (Wednesday, 26 July)
• Re: [w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36) (Wednesday, 26 July)
• [w3c/payment-method-basic-card] Unclear what happens when there are duplicates (#36) (Wednesday, 26 July)
• Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173) (Tuesday, 25 July)
• Re: [w3c/payment-request] Use first matching PaymentDetailsModifier (#541) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Remove wallets, clean up issues (#188) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Remove wallets, clean up issues (#188) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Add .clear() to map-likes (#129) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Add .clear() to map-likes (#129) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189) (Tuesday, 25 July)
• Re: [w3c/payment-request] editorial: fix CR exit date, add exit criteria (#563) (Tuesday, 25 July)
• Re: [w3c/payment-request] editorial: set CR end date to 31st oct (#562) (Tuesday, 25 July)
• Re: [w3c/payment-request] editorial: set CR end date to 31st oct (#562) (Tuesday, 25 July)
• Re: [w3c/payment-request] editorial: fix CR exit date, add exit criteria (#563) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189) (Monday, 24 July)
• Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189) (Monday, 24 July)
• Re: [w3c/payment-handler] Changed Jason to Andre per their request (#189) (Monday, 24 July)
• Re: [w3c/payment-method-id] Auto-publishing failing on bad token (#43) (Monday, 24 July)
• Re: [w3c/payment-method-id] Auto-publishing failing on bad token (#43) (Monday, 24 July)
• Re: [w3c/browser-payment-api] editorial: fix CR exit date, add exit criteria (#563) (Monday, 24 July)
• Re: [w3c/payment-method-id] CR checklist (#39) (Monday, 24 July)
• Re: [w3c/browser-payment-api] validate supportedMethods (#464) (Monday, 24 July)
• Re: [w3c/browser-payment-api] Reject acceptedPromise if payment method identifer is invalid (#557) (Monday, 24 July)
• Re: [w3c/browser-payment-api] Reject acceptedPromise if payment method identifer is invalid (#557) (Monday, 24 July)
• Re: [w3c/payment-handler] Remove wallets, clean up issues (#188) (Monday, 24 July)
• Re: [w3c/payment-handler] Remove wallets, clean up issues (#188) (Monday, 24 July)
• Re: [w3c/payment-handler] Remove wallets, clean up issues (#188) (Monday, 24 July)
• Re: [w3c/payment-handler] Remove wallets, clean up issues (#188) (Monday, 24 July)
• Re: [w3c/payment-handler] Remove wallets, clean up issues (#188) (Monday, 24 July)
• Re: [w3c/payment-handler] Remove wallets, clean up issues (#188) (Monday, 24 July)
• Re: [w3c/browser-payment-api] chore: rename repo to match shortname (#564) (Monday, 24 July)
• Re: [w3c/browser-payment-api] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Monday, 24 July)
• Re: [w3c/browser-payment-api] Populate implementation report (#560) (Monday, 24 July)
• Re: [w3c/browser-payment-api] Populate implementation report (#560) (Monday, 24 July)
• Re: [w3c/browser-payment-api] Add implementation report (#560) (Monday, 24 July)
• [w3c/browser-payment-api] chore: rename repo to match shortname (#564) (Monday, 24 July)
• [w3c/payment-method-id] Auto-publishing failing on bad token (#43) (Monday, 24 July)
• [w3c/payment-method-id] editorial: add CR exit criteria (#42) (Monday, 24 July)
• [w3c/browser-payment-api] editorial: fix CR exit date, add exit criteria (#563) (Monday, 24 July)
• Re: [w3c/browser-payment-api] editorial: set CR end date to 31st oct (#562) (Monday, 24 July)
• Re: [w3c/browser-payment-api] editorial: set CR end date to 31st oct (#562) (Monday, 24 July)
• Re: [w3c/payment-method-id] CR checklist (#39) (Monday, 24 July)
• Re: [w3c/payment-method-id] CR checklist (#39) (Monday, 24 July)
• [w3c/payment-method-id] Clarify validation of standardized PMIs (#41) (Monday, 24 July)
• [w3c/payment-method-id] make fetching URL-PMI optional (closes #33) (#40) (Monday, 24 July)
• Re: [w3c/payment-method-id] CR checklist (#39) (Friday, 21 July)
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Friday, 21 July)
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Friday, 21 July)
• Re: [w3c/browser-payment-api] editorial: set CR end date to 31st oct (#562) (Friday, 21 July)
• Re: [w3c/browser-payment-api] editorial: set CR end date to 31st oct (#562) (Friday, 21 July)
• [w3c/browser-payment-api] editorial: set CR end date to 31st oct (#562) (Friday, 21 July)
• Re: [w3c/payment-method-basic-card] Rename repo to match shortname (#33) (Friday, 21 July)
• Re: [w3c/payment-method-basic-card] chore: fix links from rename (#35) (Friday, 21 July)
• [w3c/webpayments-methods-card] chore: fix links from rename (#35) (Friday, 21 July)
• [w3c/webpayments-methods-card] Processing note should be normative text (#34) (Friday, 21 July)
• [w3c/webpayments-methods-card] Rename repo to match shortname (#33) (Friday, 21 July)
• Re: [w3c/browser-payment-api] Editorial: move+rework examples (#553) (Thursday, 20 July)
• Re: [w3c/browser-payment-api] Move examples to top of document (#456) (Thursday, 20 July)
• Re: [w3c/browser-payment-api] Editorial: move+rework examples (#553) (Thursday, 20 July)
• Re: [w3c/browser-payment-api] Editorial: move+rework examples (#553) (Thursday, 20 July)
• Re: [w3c/browser-payment-api] Editorial: move+rework examples (#553) (Thursday, 20 July)
• Re: [w3c/browser-payment-api] Editorial: move+rework examples (#553) (Thursday, 20 July)
• Re: [w3c/payment-method-id] Rename repo payment-method-id (#38) (Thursday, 20 July)
• Re: [w3c/payment-method-id] Rename repo payment-method-id (#38) (Thursday, 20 July)
• Re: [w3c/payment-method-id] Rename repo payment-method-id (#38) (Thursday, 20 July)
• Re: [w3c/payment-method-id] Rename repo payment-method-id (#38) (Wednesday, 19 July)
• Re: [w3c/payment-method-id] Rename repo payment-method-id (#38) (Wednesday, 19 July)
• [w3c/browser-payment-api] Make privacy section normative (closes #439) (#561) (Tuesday, 18 July)
• Re: [w3c/browser-payment-api] editorial: Clarify wording to not imply 'pull' only payments (#474) (Tuesday, 18 July)
• Re: [w3c/browser-payment-api] editorial: Clarify wording to not imply 'pull' only payments (#474) (Tuesday, 18 July)
• Re: [w3c/browser-payment-api] Use first matching PaymentDetailsModifier (#541) (Tuesday, 18 July)
• Re: [w3c/browser-payment-api] Editorial changes (#559) (Tuesday, 18 July)
• Re: [w3c/browser-payment-api] Editorial changes (#559) (Tuesday, 18 July)
• Re: [w3c/webpayments-method-identifiers] CR checklist (#39) (Tuesday, 18 July)
• Re: [w3c/webpayments-method-identifiers] Rename repo payment-method-id (#38) (Tuesday, 18 July)
• Re: [w3c/webpayments-method-identifiers] Rename repo payment-method-id (#38) (Tuesday, 18 July)
• Re: [w3c/browser-payment-api] Editorial changes (#559) (Tuesday, 18 July)
• Re: [w3c/browser-payment-api] Editorial changes (#559) (Tuesday, 18 July)
• Re: [w3c/browser-payment-api] Editorial changes (#559) (Tuesday, 18 July)
• Re: [w3c/browser-payment-api] Editorial changes (#559) (Tuesday, 18 July)
• [w3c/webpayments-method-identifiers] CR checklist (#39) (Tuesday, 18 July)
• [w3c/webpayments-method-identifiers] Rename repo payment-method-id (#38) (Tuesday, 18 July)
• Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) (Tuesday, 18 July)
• Re: [w3c/browser-payment-api] CR check list (#520) (Monday, 17 July)
• [w3c/browser-payment-api] Add implementation report (#560) (Monday, 17 July)
• Re: [w3c/browser-payment-api] Editorial changes (#559) (Monday, 17 July)
• Re: [w3c/browser-payment-api] UX guidance article (#558) (Friday, 14 July)
• Re: [w3c/browser-payment-api] UX guidance article (#558) (Friday, 14 July)
• Re: [w3c/browser-payment-api] UX guidance article (#558) (Friday, 14 July)
• Re: [w3c/browser-payment-api] Drop array support for supported methods? (#549) (Tuesday, 11 July)
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Monday, 10 July)
• Re: [w3c/browser-payment-api] UX guidance article (#558) (Thursday, 6 July)
• Re: [w3c/browser-payment-api] UX guidance article (#558) (Wednesday, 5 July)

Marijn Kruisselbrink

• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) (Tuesday, 25 July)
• [w3c/payment-handler] The Open Window Algorithm tries to access [[state]] of a request in a way that doesn't make sense (#192) (Monday, 24 July)
• Re: [w3c/payment-handler] respondWith behavior not specified (#190) (Monday, 24 July)
• [w3c/payment-handler] "PaymentRequestEvent dictionary" makes no sense (#191) (Monday, 24 July)
• [w3c/payment-handler] respondWith behavior not specified (#190) (Monday, 24 July)

mattsaxon

• Re: [w3c/webpayments-methods-tokenization] Should the response data include an "expires" field? (#12) (Tuesday, 25 July)
• Re: [w3c/webpayments-methods-tokenization] Structuring the tokenization payment method(s) (#13) (Tuesday, 25 July)
• [w3c/webpayments-methods-tokenization] multiuse flow (#20) (Tuesday, 25 July)
• [w3c/webpayments-methods-tokenization] Need for environment parameter (#19) (Tuesday, 25 July)
• [w3c/webpayments-methods-tokenization] tokenProviderMerchantIdentifier vs merchantId (#18) (Tuesday, 25 July)
• [w3c/webpayments-methods-tokenization] Linkage to BasicCard Spec (#17) (Tuesday, 25 July)
• [w3c/webpayments-methods-tokenization] Where does tokenisation occur in the the flow - and do we care (#16) (Tuesday, 25 July)
• [w3c/webpayments-methods-tokenization] change field name of oneTimeUse to singleUse (#15) (Tuesday, 25 July)
• [w3c/webpayments-methods-tokenization] Should the tokenization task force standardize an interface between payment apps and tokenization service providers? (#14) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) (Tuesday, 25 July)

Michael[tm] Smith

• Re: [w3c/payment-request] Populate implementation report (#560) (Monday, 24 July)
• Re: [w3c/browser-payment-api] chore: rename repo to match shortname (#564) (Monday, 24 July)
• Re: [w3c/browser-payment-api] chore: rename repo to match shortname (#564) (Monday, 24 July)

Mustafa Kurtuldu

• Re: [w3c/browser-payment-api] UX guidance article (#558) (Monday, 10 July)
• Re: [w3c/browser-payment-api] UX guidance article (#558) (Wednesday, 5 July)

Olivier Yiptong

• Re: [w3c/webpayments-methods-tokenization] Allow merchant to specify multiple Tokenization Providers (#11) (Tuesday, 25 July)
• Re: [w3c/webpayments-methods-tokenization] Allow merchant to specify multiple Tokenization Providers (#11) (Tuesday, 25 July)
• Re: [w3c/webpayments-methods-tokenization] Should the response data include an "expires" field? (#12) (Tuesday, 25 July)
• Re: [w3c/webpayments-methods-tokenization] Should we keep the IIN/BIN or drop it from the spec? (#10) (Tuesday, 25 July)
• Re: [w3c/webpayments-methods-tokenization] Should we keep the IIN/BIN or drop it from the spec? (#10) (Tuesday, 25 July)
• Re: [w3c/webpayments-methods-tokenization] Allow merchant to specify multiple Tokenization Providers (#11) (Tuesday, 11 July)
• Re: [w3c/webpayments-methods-tokenization] Allow merchant to specify multiple Tokenization Providers (#11) (Tuesday, 11 July)
• [w3c/webpayments-methods-tokenization] Allow merchant to specify multiple Tokenization Providers (#11) (Tuesday, 11 July)
• Re: [w3c/webpayments-methods-tokenization] Should we keep the IIN/BIN or drop it from the spec? (#10) (Tuesday, 11 July)

Rouslan Solomakhin

• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Sunday, 30 July)
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Friday, 28 July)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Friday, 28 July)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Friday, 28 July)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Friday, 28 July)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Friday, 28 July)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Friday, 28 July)
• Re: [w3c/payment-method-basic-card] editorial: cleanup, tidy, ReSpec warns, etc. (#37) (Wednesday, 26 July)
• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) (Tuesday, 25 July)
• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) (Tuesday, 25 July)
• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Monday, 24 July)
• Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173) (Friday, 21 July)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Tuesday, 11 July)
• Re: [w3c/payment-handler] PaymentRequestEvent.total should be PaymentCurrencyAmount. (#187) (Thursday, 6 July)
• Re: [w3c/payment-handler] PaymentRequestEvent.total should be PaymentCurrencyAmount. (#187) (Thursday, 6 July)
• Re: [w3c/payment-handler] PaymentRequestEvent.total should be PaymentCurrencyAmount. (#187) (Thursday, 6 July)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent and AbortPaymentEvent. (#170) (Wednesday, 5 July)

Zach Koch

• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Friday, 28 July)
• [w3c/payment-request] Considering allowing merchants to populate set of shipping addresses (#565) (Friday, 28 July)
• Re: [w3c/payment-method-id] Clarify validation of standardized PMIs (#41) (Wednesday, 26 July)
• Re: [w3c/payment-method-id] Clarify validation of standardized PMIs (#41) (Wednesday, 26 July)
• Re: [w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36) (Wednesday, 26 July)
• Re: [w3c/payment-method-basic-card] Unclear what happens when there are duplicates? (#36) (Wednesday, 26 July)
• Re: [w3c/browser-payment-api] Remove 2119 language from privacy section. (#511) (Wednesday, 19 July)
• Re: [w3c/browser-payment-api] Remove 2119 language from privacy section. (#511) (Wednesday, 19 July)
• Re: [w3c/browser-payment-api] WIP: move+rework examples (#553) (Wednesday, 19 July)
• Re: [w3c/browser-payment-api] Make privacy section normative (closes #439) (#561) (Wednesday, 19 July)
• Re: [w3c/browser-payment-api] Make privacy section normative (closes #439) (#561) (Wednesday, 19 July)
• Re: [w3c/browser-payment-api] RFC2119 keywords in informative sections (#439) (Wednesday, 19 July)
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Friday, 7 July)

Last message date: Monday, 31 July 2017 13:25:06 UTC