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

Saturday, 30 September 2017

• Re: [w3c/payment-request] onpaymentchange event to validate payment details (#634) chinnagogulapati

Friday, 29 September 2017

• Re: [w3c/payment-handler] Allow Payment instrument to respond with user data (#218) Adrian Hope-Bailie
• Re: [w3c/payment-request] onpaymentchange event to validate payment details (#634) Adrian Hope-Bailie
• [w3c/payment-handler] Allow Payment instrument to respond with user data (#218) Krystian Czesak
• Re: [w3c/payment-request] onpaymentchange event to validate payment details (#634) Marcos Cáceres
• Re: [w3c/payment-request] onpaymentchange event to validate payment details (#634) Rouslan Solomakhin
• [w3c/payment-request] onpaymentchange event to validate payment details (#634) Dan Dascalescu

Thursday, 28 September 2017

• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) Rouslan Solomakhin

Wednesday, 27 September 2017

• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) Adrian Hope-Bailie
• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) Adrian Hope-Bailie
• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) Anders Rundgren
• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) ianbjacobs
• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) Chad Campbell
• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) Chad Campbell
• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) Rouslan Solomakhin
• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) Marcos Cáceres
• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) ianbjacobs
• [w3c/payment-request] Feature Request - Pre Authorization (#633) Chad Campbell
• Re: [w3c/payment-request] Regulatory Compliance Support (#632) Mark Richards
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) carinsuranceadvice
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) carinsuranceadvice
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) carinsuranceadvice

Tuesday, 26 September 2017

• Re: [w3c/payment-request] Regulatory Compliance Support (#632) ianbjacobs
• Re: [w3c/payment-request] Regulatory Compliance Support (#632) Marcos Cáceres
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) Marcos Cáceres
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) Marcos Cáceres
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) Marcos Cáceres
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) Marcos Cáceres
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) ianbjacobs

Monday, 25 September 2017

• Re: [w3c/payment-request] Regulatory Compliance Support (#632) Mark Richards
• Re: [w3c/payment-request] After CR, evaluate if paymentRequest.id being a UUID is a must (#588) Marcos Cáceres
• Re: [w3c/payment-request] Should user agent validate currency? (#490) Marcos Cáceres
• Re: [w3c/payment-request] Should user agent validate currency? (#490) Marcos Cáceres
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) Marcos Cáceres
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) Marcos Cáceres
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) Marcos Cáceres
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) Marcos Cáceres
• Re: [w3c/payment-request] Regulatory Compliance Support (#632) Marcos Cáceres

Saturday, 23 September 2017

• [w3c/payment-request] Regulatory Compliance Support (#632) Mark Richards

Friday, 22 September 2017

• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) ianbjacobs
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) ianbjacobs
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) Mark Richards
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) Marcos Cáceres
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Gather default test data values (#41) Marcos Cáceres
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) Marcos Cáceres
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) Marcos Cáceres
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) ianbjacobs
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) Marcos Cáceres
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) Marcos Cáceres
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) ashok
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) ianbjacobs
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) Marcos Cáceres

Thursday, 21 September 2017

• [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) ianbjacobs
• Re: [w3c/payment-method-basic-card] Gather default test data values (#41) ianbjacobs
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) Mark Richards
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) Dave Longley
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) Adrian Hope-Bailie
• Re: [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) ianbjacobs
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) Marcos Cáceres
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) Marcos Cáceres
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) Mark Richards
• [w3c/payment-request] 404 on some tests (#630) Marcos Cáceres
• Re: [w3c/payment-handler] Add [Exposed] to PaymentInstruments interface. (#216) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Propose text about why the api can reduce need; without any recommendations (#16) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Editorial: use Adam's text as intro (#42) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Editorial: use Adam's text as intro (#42) Marcos Cáceres
• Re: [w3c/payment-request] Make iframe allowpaymentrequest normative (#618) Marcos Cáceres
• Re: [w3c/payment-request] Make iframe allowpaymentrequest normative (#618) Marcos Cáceres
• Re: [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) Marcos Cáceres
• Re: [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) Lukasz Olejnik
• Re: [w3c/payment-request] Make iframe allowpaymentrequest normative (#618) Domenic Denicola
• Re: [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) Marcos Cáceres
• [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) Domenic Denicola
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) Marcos Cáceres
• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) ianbjacobs

Wednesday, 20 September 2017

• Re: [w3c/payment-method-basic-card] Gather default test data values (#41) Adrian Hope-Bailie
• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) Jinho Bang
• Re: [w3c/payment-method-basic-card] Editorial: use Adam's text as intro (#42) ianbjacobs
• Re: [w3c/payment-method-basic-card] Editorial: use Adam's text as intro (#42) ianbjacobs
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) ianbjacobs
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) ianbjacobs
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) Rouslan Solomakhin
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) Mark Richards
• [w3c/payment-method-basic-card] Things needed to publish as note (#43) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Editorial: use Adam's text as intro (#42) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Gather default test data values (#41) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Standardize `environment` member (#41) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] PaymentResponse missing filters (#28) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] PaymentResponse missing filters (#28) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] PaymentResponse missing filters (#28) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] PaymentResponse missing filters (#28) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Add text about why the api can reduce need to store credit card information (#18) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Add text about why the api can reduce need to store credit card information (#18) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Editorial: use Adam's text as intro (#42) Marcos Cáceres
• [w3c/payment-method-basic-card] Editorial: use Adam's text as intro (#42) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Relationship to PaymentRequest (#40) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Relationship to PaymentRequest (#40) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) Marcos Cáceres
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) Marcos Cáceres
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) ianbjacobs
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) Marcos Cáceres
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) Marcos Cáceres
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Standardize `environment` member (#41) Adrian Hope-Bailie

Tuesday, 19 September 2017

• [w3c/payment-request] Suggested emphasis of privacy protections (#628) Mark Richards
• Re: [w3c/payment-method-basic-card] Standardize `environment` member (#41) Marcos Cáceres
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) Mark Richards
• Re: [w3c/payment-request] Add support for crypto currencies (#627) ianbjacobs
• Re: [w3c/payment-request] Add support for crypto currencies (#627) ianbjacobs
• [w3c/payment-request] Add support for crypto currencties (#627) AhsanEjaz
• Re: [w3c/payment-handler] Make explicit which origin to use in conjunction with payment method manifest. (#209) Rouslan Solomakhin
• Re: [w3c/payment-handler] Make explicit which origin to use in conjunction with payment method manifest. (#209) ianbjacobs
• Re: [w3c/payment-handler] Make explicit which origin to use in conjunction with payment method manifest. (#209) Rouslan Solomakhin
• Re: [w3c/payment-handler] Make explicit which origin to use in conjunction with payment method manifest. (#209) Rouslan Solomakhin
• Re: [w3c/payment-handler] Security addition (#214) Rouslan Solomakhin
• Re: [w3c/payment-handler] Security addition (#214) ianbjacobs
• Re: [w3c/payment-handler] Security addition (#214) ianbjacobs
• Re: [w3c/payment-handler] Security addition (#214) ianbjacobs
• Re: [w3c/payment-handler] Removed section on instrument grouping with closure of issue 153 (#213) ianbjacobs
• Re: [w3c/payment-handler] Removed section on instrument grouping with closure of issue 153 (#213) Rouslan Solomakhin
• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) ianbjacobs
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) Marcos Cáceres
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) Rouslan Solomakhin
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) Marcos Cáceres
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) ianbjacobs
• Re: [w3c/payment-request] Implementation of PaymentAddress.languageCode (#608) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Standardize `environment` member (#41) Marcos Cáceres
• Re: [w3c/payment-request] Implementation of PaymentAddress.languageCode (#608) Marcos Cáceres
• [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) Marcos Cáceres
• Re: [w3c/payment-request] Should user agent validate currency? (#490) Marcos Cáceres
• Re: [w3c/payment-request] Should user agent validate currency? (#490) ianbjacobs
• Re: [w3c/payment-request] Should user agent validate currency? (#490) Marcos Cáceres
• Re: [w3c/payment-request] Should user agent validate currency? (#490) Domenic Denicola
• Re: [w3c/payment-request] Should user agent validate currency? (#490) ianbjacobs
• Re: [w3c/payment-request] Should user agent validate currency? (#490) Marcos Cáceres
• Re: [w3c/payment-request] Should user agent validate currency? (#490) Marcos Cáceres
• Re: [w3c/payment-request] Should user agent validate currency? (#490) ianbjacobs
• Re: [w3c/payment-request] Should user agent validate currency? (#490) Adrian Hope-Bailie
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) Marcos Cáceres
• Re: [w3c/payment-request] Documentation error? 55 + 5 = 65 (#622) Marcos Cáceres
• [w3c/payment-request] Move to an incremental feature release model (#625) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) ianbjacobs
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) ianbjacobs
• Re: [w3c/payment-request] Should user agent validate currency? (#490) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres

Monday, 18 September 2017

• Re: [w3c/payment-request] Pay method for testing environment (#613) sabrinatseng
• Re: [w3c/payment-request] Should user agent validate currency? (#490) Adrian Hope-Bailie
• Re: [w3c/payment-request] Should user agent validate currency? (#490) Adrian Hope-Bailie
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) ianbjacobs
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) Adrian Hope-Bailie
• Re: [w3c/payment-request] Pay method for testing environment (#613) Adrian Hope-Bailie
• Re: [w3c/payment-request] Pay method for testing environment (#613) Adrian Hope-Bailie
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) Rouslan Solomakhin
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) ianbjacobs
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) Rouslan Solomakhin
• [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) ianbjacobs
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) Rouslan Solomakhin
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) ianbjacobs
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) Rouslan Solomakhin
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) ianbjacobs
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) Rouslan Solomakhin
• [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) ianbjacobs
• Re: [w3c/payment-handler] Add [Exposed] to all interfaces (#215) ianbjacobs
• Re: [w3c/payment-handler] Add [Exposed] to PaymentInstruments interface. (#216) ianbjacobs
• Re: [w3c/payment-handler] Add [Exposed] to PaymentInstruments interface. (#216) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add [Exposed] to PaymentInstruments interface. (#216) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add [Exposed] to PaymentInstruments interface. (#216) Rouslan Solomakhin
• Re: [w3c/payment-request] Implementation of PaymentAddress.languageCode (#608) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add [Exposed] to PaymentInstruments interface. (#216) Jinho Bang
• [w3c/payment-handler] Add [Exposed] to PaymentInstruments interface. (#216) Jinho Bang
• Re: [w3c/payment-request] Documentation error? 55 + 5 = 65 (#622) Marcos Cáceres
• Re: [w3c/payment-request] Documentation error? 55 + 5 = 65 (#622) Marcos Cáceres
• Re: [w3c/payment-request] Typo fix (#623) Marcos Cáceres
• Re: [w3c/payment-request] Typo fix (#623) Marcos Cáceres
• Re: [w3c/payment-request] Documentation error? 55 + 5 = 65 (#622) Marcos Cáceres
• [w3c/payment-request] Typo fix (#623) Terence Eden
• [w3c/payment-request] Documentation error? 55 + 5 = 65 (#622) Terence Eden
• Re: [w3c/payment-request] Implementation of PaymentAddress.languageCode (#608) Marcos Cáceres
• Re: [w3c/payment-method-id] Auto publication no longer needed (#51) Marcos Cáceres

Friday, 15 September 2017

• [w3c/payment-handler] Add [Exposed] to all interfaces (#215) Anne van Kesteren
• Re: [w3c/payment-method-id] Auto publication no longer needed (#51) Denis Ah-Kang
• Re: [w3c/payment-method-id] Auto publication no longer needed (#51) Marcos Cáceres
• Re: [w3c/payment-method-id] Auto publication no longer needed (#51) Marcos Cáceres
• Re: [w3c/payment-request] Auto publication no longer needed (#621) Marcos Cáceres
• [w3c/payment-method-id] Auto publication no longer needed (#51) Denis Ah-Kang
• [w3c/payment-request] Auto publication no longer needed (#621) Denis Ah-Kang
• Re: [w3c/payment-method-basic-card] Standardize `environment` member (#41) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Processing note should be normative text (#34) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Clarify the required behaviour for options parameters (#26) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Clarify this specification is intended to become a W3C Note (#27) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Define processing model (#39) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] list/registry of approved card network identifiers should be listed in references section (#32) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) sabrinatseng
• Re: [w3c/payment-method-basic-card] Standardize `environment` member (#41) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) sabrinatseng
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres
• [w3c/payment-method-basic-card] Standardize `environment` member (#41) Marcos Cáceres

Thursday, 14 September 2017

• Re: [w3c/payment-request] Pay method for testing environment (#613) Adrian Hope-Bailie
• Re: [w3c/payment-request] Pay method for testing environment (#613) Adrian Hope-Bailie
• Re: [w3c/payment-request] Pay method for testing environment (#613) Adrian Hope-Bailie
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) Rouslan Solomakhin
• Re: [w3c/payment-request] .updateWith() example says "throws" (#620) Marcos Cáceres
• Re: [w3c/payment-request] .updateWith() example says "throws" (#620) Marcos Cáceres
• [w3c/payment-request] .updateWith() example says "throws" (#620) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres

Wednesday, 13 September 2017

• Re: [w3c/payment-request] Chore: Minor link fix (#619) Marcos Cáceres
• Re: [w3c/payment-request] Chore: Minor link fix (#619) Marcos Cáceres
• [w3c/payment-request] Chore: Minor link fix (#619) ianbjacobs
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Marcos Cáceres

Tuesday, 12 September 2017

• Re: [w3c/payment-request] Section for A11Y Considerations (#450) chaals
• [w3c/payment-request] Candidate Recommendation Marcos Cáceres
• [w3c/payment-request] Make iframe allowpaymentrequest normative (#618) Marcos Cáceres

Monday, 11 September 2017

• [w3c/payment-request] Decide on currencySystem (#617) Marcos Cáceres

Friday, 8 September 2017

• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Adrian Hope-Bailie
• Re: [w3c/payment-request] Editorial: removed extra "the" (#616) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: removed extra "the" (#616) Marcos Cáceres
• [w3c/payment-request] Editorial: removed extra "the" (#616) ianbjacobs
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Rouslan Solomakhin
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Rouslan Solomakhin
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Rouslan Solomakhin
• Re: [w3c/payment-request] 'Pull' Payment Bias in API spec (#499) ianbjacobs
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Marcos Cáceres
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Marcos Cáceres
• Re: [w3c/payment-request] shippingOption description is misleading (#534) Marcos Cáceres
• Re: [w3c/payment-request] shippingOption description is misleading (#534) Marcos Cáceres
• Re: [w3c/payment-request] 'Pull' Payment Bias in API spec (#499) Marcos Cáceres
• Re: [w3c/payment-request] 'Pull' Payment Bias in API spec (#499) Marcos Cáceres
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) Marcos Cáceres
• Re: [w3c/payment-request] Creation and assignment of PaymentAddress is underspecified (#603) Marcos Cáceres
• Re: [w3c/payment-request] .updateWith() should only be callable if event was canceled (#589) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) Marcos Cáceres
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) Marcos Cáceres
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Marcos Cáceres
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Marcos Cáceres
• Re: [w3c/payment-request] Pre-filter shipping addresses, e.g. by country (#614) Dan Dascalescu
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) Marcos Cáceres
• Re: [w3c/payment-request] Pre-filter shipping addresses, e.g. by country (#614) Marcos Cáceres
• Re: [w3c/payment-request] Only select shippingOption if asked to (closes #609) (#610) Marcos Cáceres
• Re: [w3c/payment-request] If requestShipping is false, pr.shippingOption should be null (#609) Marcos Cáceres

Thursday, 7 September 2017

• Re: [w3c/payment-request] Pay method for testing environment (#613) sabrinatseng
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) Domenic Denicola
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Rouslan Solomakhin
• [w3c/payment-request] Pre-calculate shipping costs for available addresses (#615) Dan Dascalescu
• [w3c/payment-request] Pre-filter shipping addresses, e.g. by country (#614) Dan Dascalescu
• Re: [w3c/payment-request] Pay method for testing environment (#613) Rouslan Solomakhin
• Re: [w3c/payment-request] Pay method for testing environment (#613) sabrinatseng
• Re: [w3c/payment-request] Do not show payment requests for non-fully-active documents (#579) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) sabrinatseng
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres
• Re: [w3c/payment-request] Pay method for testing environment (#613) sabrinatseng
• Re: [w3c/payment-request] Pay method for testing environment (#613) Marcos Cáceres
• [w3c/payment-request] Pay method for testing environment (#613) sabrinatseng
• Re: [w3c/payment-request] Only select shippingOption if asked to (closes #609) (#610) Marcos Cáceres
• Re: [w3c/payment-request] Only select shippingOption if asked to (closes #609) (#610) Marcos Cáceres
• Re: [w3c/payment-method-id] Clarify CR exit requirements (#50) Marcos Cáceres
• Re: [w3c/payment-request] Clarify CR exit requirements (#598) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: explicitly Expose=Window IDL interface (#612) Marcos Cáceres
• Re: [w3c/payment-request] Add Exposed= to IDL interfaces (#611) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: explicitly Expose=Window IDL interface (#612) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: explicitly Expose=Window IDL interface (#612) Domenic Denicola
• Re: [w3c/payment-request] Editorial: explicitly Expose=Window IDL interface (#612) Marcos Cáceres
• [w3c/payment-request] Editorial: explicitly Expose=Window IDL interface (#612) Marcos Cáceres

Wednesday, 6 September 2017

• Re: [w3c/payment-request] PayerAddress.phone and PayerResponse.payerPhone (#606) Marcos Cáceres
• Re: [w3c/payment-request] PayerAddress.phone and PayerResponse.payerPhone (#606) Marcos Cáceres
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Rouslan Solomakhin
• Re: [w3c/payment-request] PayerAddress.phone and PayerResponse.payerPhone (#606) Zach Koch
• [w3c/payment-request] Add Exposed= to IDL interfaces (#611) Marcos Cáceres
• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) ianbjacobs
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) Marcos Cáceres
• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) KJM
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Marcos Cáceres
• Re: [w3c/payment-handler] Security addition (#214) ianbjacobs
• Re: [w3c/payment-handler] Security addition (#214) ianbjacobs
• Re: [w3c/payment-handler] Security addition (#214) ianbjacobs
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Rouslan Solomakhin
• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) KJM
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) Marcos Cáceres
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) Marcos Cáceres
• Re: [w3c/payment-handler] Security addition (#214) Marcos Cáceres
• Re: [w3c/payment-handler] Security addition (#214) Marcos Cáceres
• Re: [w3c/payment-handler] Security addition (#214) Marcos Cáceres
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Marcos Cáceres
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) Domenic Denicola
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) Marcos Cáceres
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) Marcos Cáceres
• Re: [w3c/payment-request] Implementation examples of PaymentAddress.languageCode (#608) Marcos Cáceres

Tuesday, 5 September 2017

• Re: [w3c/payment-request] Only select shippingOption if asked to (closes #609) (#610) Domenic Denicola
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) Domenic Denicola
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Adrian Hope-Bailie
• [w3c/payment-handler] Security addition (#214) ianbjacobs
• Re: [w3c/payment-request] PayerAddress.phone and PayerResponse.payerPhone (#606) Marcos Cáceres
• Re: [w3c/payment-request] PayerAddress.phone and PayerResponse.payerPhone (#606) Rouslan Solomakhin
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Marcos Cáceres
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Marcos Cáceres
• Re: [w3c/payment-request] PayerAddress.phone and PayerResponse.payerPhone (#606) Marcos Cáceres
• [w3c/payment-handler] Removed section on instrument grouping with closure of issue 153 (#213) ianbjacobs
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) ianbjacobs
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) ianbjacobs
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) Rouslan Solomakhin
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) ianbjacobs
• Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173) ianbjacobs
• Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173) ianbjacobs
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Fredrik Roubert
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) ianbjacobs
• Re: [w3c/payment-handler] Clarification of "instrumentKey" language (#212) Rouslan Solomakhin
• Re: [w3c/payment-handler] Clarification of "instrumentKey" language (#212) Rouslan Solomakhin
• [w3c/payment-handler] Clarification of "instrumentKey" language (#212) Mathieu Perreault
• Re: [w3c/payment-handler] Clarify empty instrument key meaning. (#208) ianbjacobs
• Re: [w3c/payment-request] PayerAddress.phone and PayerResponse.payerPhone (#606) Rouslan Solomakhin
• Re: [w3c/payment-request] Implementation examples of PaymentAddress.languageCode (#608) Rouslan Solomakhin
• Re: [w3c/payment-request] If requestShipping is false, pr.shippingOption should be null (#609) Rouslan Solomakhin
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Rouslan Solomakhin
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) ianbjacobs
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) ianbjacobs
• Re: [w3c/payment-request] If requestShipping is false, pr.shippingOption should be null (#609) Marcos Cáceres
• Re: [w3c/payment-request] If requestShipping is false, pr.shippingOption should be null (#609) Marcos Cáceres
• [w3c/payment-request] Only select shippingOption if asked to (closes #609) (#610) Marcos Cáceres
• Re: [w3c/payment-request] If requestShipping is false, pr.shippingOption should be null (#609) Marcos Cáceres
• Re: [w3c/payment-request] If requestShipping is false, pr.shippingOption should be null (#609) Marcos Cáceres
• Re: [w3c/payment-request] If requestShipping is false, pr.shippingOption should be null (#609) Marcos Cáceres
• [w3c/payment-request] If requestShipping is false, pr.shippingOption should be null (#609) Marcos Cáceres
• [w3c/payment-request] Implementation examples of PaymentAddress.languageCode (#608) Marcos Cáceres
• [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) Marcos Cáceres
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Marcos Cáceres
• Re: [w3c/payment-request] Fix PaymentAddress attr definition (closes #601) (#604) Marcos Cáceres
• Re: [w3c/payment-request] Fix PaymentAddress attr definition (closes #601) (#604) Marcos Cáceres
• Re: [w3c/payment-request] Canonicalize PaymentAddress.languageCode (closes #602) (#605) Marcos Cáceres
• Re: [w3c/payment-request] Canonicalize PaymentAddress.languageCode (closes #602) (#605) Marcos Cáceres
• Re: [w3c/payment-request] PaymentAddress.languageCode lacking canonical form (#602) Marcos Cáceres
• Re: [w3c/payment-request] Canonicalize PaymentAddress.languageCode (closes #602) (#605) Domenic Denicola
• Re: [w3c/payment-request] Canonicalize PaymentAddress.languageCode (closes #602) (#605) Marcos Cáceres
• Re: [w3c/payment-request] Fix PaymentAddress attr definition (closes #601) (#604) Domenic Denicola
• Re: [w3c/payment-request] Canonicalize PaymentAddress.languageCode (closes #602) (#605) Domenic Denicola
• [w3c/payment-request] PayerAddress.phone and PayerResponse.payerPhone (#606) Marcos Cáceres
• [w3c/payment-request] Canonicalize PaymentAddress.languageCode (closes #602) (#605) Marcos Cáceres
• [w3c/payment-request] Fix PaymentAddress attr definition (closes #601) (#604) Marcos Cáceres
• [w3c/payment-request] Creation and assignment of PaymentAddress is underspecified (#603) Marcos Cáceres
• [w3c/payment-request] PaymentAddress.languageCode lacking canonical form (#602) Marcos Cáceres
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Marcos Cáceres
• [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres

Monday, 4 September 2017

• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) Jinho Bang
• Re: [w3c/payment-request] Duplicate shippingOptions lead to inconsistent `updateWith()` - should throw! (#594) Marcos Cáceres
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (#596) Marcos Cáceres
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (#596) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Populate implementation report (#560) Marcos Cáceres
• Re: [w3c/payment-request] CR check list (#520) Marcos Cáceres
• Re: [w3c/payment-request] CR check list (#520) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Define processing model (#39) Marcos Cáceres
• [w3c/payment-request] Integration with Feature Policy (#600) Marcos Cáceres

Friday, 1 September 2017

• Re: [w3c/payment-request] Less pull centric (#599) Marcos Cáceres
• Re: [w3c/payment-request] Less pull centric (#599) Marcos Cáceres
• Re: [w3c/payment-request] editorial: Clarify wording to not imply 'pull' only payments (#474) ianbjacobs
• [w3c/payment-request] Less pull centric (#599) ianbjacobs
• Re: [w3c/payment-request] Clarify CR exit requirements (#598) ianbjacobs
• Re: [w3c/payment-method-id] Clarify CR exit requirements (#50) ianbjacobs
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) Marcos Cáceres
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (#596) Marcos Cáceres
• Re: [w3c/payment-request] Clarify CR exit requirements (#598) Michael[tm] Smith
• Re: [w3c/payment-request] Clarify CR exit requirements (#598) Michael[tm] Smith
• Re: [w3c/payment-request] Clarify CR exit requirements (#598) Michael[tm] Smith
• Re: [w3c/payment-request] editorial: Clarify wording to not imply 'pull' only payments (#474) Marcos Cáceres
• Re: [w3c/payment-request] editorial: Clarify wording to not imply 'pull' only payments (#474) Marcos Cáceres
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (#596) Marcos Cáceres
• [w3c/payment-method-id] Clarify CR exit requirements (#50) Marcos Cáceres
• Re: [w3c/payment-request] Clarify CR exit requirements (#598) Marcos Cáceres
• Re: [w3c/payment-request] Clarify CR exit requirements (#598) Marcos Cáceres
• [w3c/payment-request] Clarify CR exit requirements (#598) Marcos Cáceres

Last message date: Saturday, 30 September 2017 17:49:53 UTC