public-webpayments-specs@w3.org from November 2018 by author

Adrian Hope-Bailie

• Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) (Tuesday, 20 November)
• Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) (Monday, 19 November)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Monday, 19 November)

aestes

• Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) (Tuesday, 27 November)
• Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) (Monday, 26 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) (Monday, 26 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) (Monday, 19 November)
• Re: [w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720) (Friday, 2 November)
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) (Friday, 2 November)
• Re: [w3c/payment-request] Add paymentMethodErrors, payerErrors, to PaymentDetailsUpdate (#768) (Friday, 2 November)
• Re: [w3c/payment-request] Rename `PayerErrorFields` to `PayerErrors` (#789) (Friday, 2 November)
• Re: [w3c/payment-request] Meaning of canMakePayment() (#800) (Friday, 2 November)
• Re: [w3c/payment-request] fix: retry()'s errorFields should be optional per WebIDL (#805) (Friday, 2 November)

Christos Constantinou

• Re: [w3c/payment-request] Support requesting billing address (#749) (Wednesday, 28 November)
• Re: [w3c/payment-request] Support requesting billing address (#749) (Tuesday, 27 November)

Danyao Wang

• Re: [w3c/payment-request] Treat scroll as a user gesture for PaymentRequest.show() (#797) (Wednesday, 7 November)
• Re: [w3c/payment-request] Treat scroll as a user gesture for PaymentRequest.show() (#797) (Wednesday, 7 November)

Domenic Denicola

• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Thursday, 29 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Thursday, 29 November)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Tuesday, 27 November)
• Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) (Tuesday, 27 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Thursday, 22 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) (Thursday, 22 November)
• Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) (Tuesday, 20 November)
• Re: [w3c/payment-request] Change what canMakePayment() means (#806) (Friday, 9 November)

ianbjacobs

• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) (Tuesday, 27 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Tuesday, 27 November)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Tuesday, 27 November)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Tuesday, 27 November)
• [w3c/payment-request] Include payment handler information in response (#815) (Tuesday, 27 November)
• Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) (Tuesday, 20 November)
• Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) (Monday, 19 November)
• Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) (Monday, 19 November)
• Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) (Tuesday, 13 November)
• Re: [w3c/payment-request] Consider specifying a testing IDL for a mock payment UI (#799) (Tuesday, 13 November)
• [w3c/webpayments-methods-tokenization] Should tokenization be a URL-based payment method? (#54) (Monday, 12 November)
• Re: [w3c/payment-request] Way of detecting if can make payment with some instrument (#801) (Wednesday, 7 November)
• Re: [w3c/payment-request] Treat scroll as a user gesture for PaymentRequest.show() (#797) (Wednesday, 7 November)
• Re: [w3c/payment-request] Way of detecting if can make payment with some instrument (#801) (Wednesday, 7 November)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Tuesday, 6 November)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Tuesday, 6 November)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Tuesday, 6 November)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Tuesday, 6 November)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Tuesday, 6 November)
• Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) (Monday, 5 November)
• Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) (Monday, 5 November)
• Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) (Thursday, 1 November)

Jenan Wise

• Re: [w3c/payment-request] Meaning of canMakePayment() (#800) (Friday, 9 November)

Jinho Bang

• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) (Monday, 5 November)
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) (Monday, 5 November)
• Re: [w3c/payment-request] fix: retry()'s should be optional per WebIDL (#805) (Thursday, 1 November)

Marcos Cáceres

• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) (Thursday, 29 November)
• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) (Thursday, 29 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Thursday, 29 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Thursday, 29 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Thursday, 29 November)
• [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) (Thursday, 29 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Thursday, 29 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Thursday, 29 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Thursday, 29 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Thursday, 29 November)
• Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) (Wednesday, 28 November)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Wednesday, 28 November)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Wednesday, 28 November)
• Re: [w3c/payment-request] Support requesting billing address (#749) (Wednesday, 28 November)
• Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) (Wednesday, 28 November)
• Re: [w3c/payment-request] Support requesting billing address (#749) (Wednesday, 28 November)
• Re: [w3c/payment-request] Support requesting billing address (#749) (Wednesday, 28 November)
• Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) (Wednesday, 28 November)
• Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) (Wednesday, 28 November)
• Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) (Wednesday, 28 November)
• Re: [w3c/payment-method-basic-card] Things needed to publish as note (#43) (Wednesday, 28 November)
• Re: [w3c/payment-method-basic-card] Things needed to publish as note (#43) (Wednesday, 28 November)
• Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) (Wednesday, 28 November)
• Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) (Wednesday, 28 November)
• Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) (Wednesday, 28 November)
• Re: [w3c/payment-request] Support requesting billing address (#749) (Wednesday, 28 November)
• Re: [w3c/payment-request] Support requesting billing address (#749) (Wednesday, 28 November)
• Re: [w3c/payment-request] Support requesting billing address (#749) (Wednesday, 28 November)
• Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) (Wednesday, 28 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) (Tuesday, 27 November)
• Re: [w3c/payment-request] Treat scroll as a user gesture for PaymentRequest.show() (#797) (Tuesday, 27 November)
• Re: [w3c/payment-request] Treat scroll as a user gesture for PaymentRequest.show() (#797) (Tuesday, 27 November)
• Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) (Tuesday, 27 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) (Tuesday, 27 November)
• [w3c/payment-request] De-duplicate "user aborts the payment request" and "abort the update (#814) (Tuesday, 27 November)
• Re: [w3c/payment-request] fix: while retrying complete() returns a rejected promise (#808) (Tuesday, 27 November)
• Re: [w3c/payment-request] fix: while retrying complete() returns a rejected promise (#808) (Tuesday, 27 November)
• Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) (Tuesday, 27 November)
• Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) (Tuesday, 27 November)
• Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) (Tuesday, 27 November)
• Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) (Tuesday, 27 November)
• Re: [w3c/payment-request] Support requesting billing address (#749) (Tuesday, 27 November)
• Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) (Monday, 26 November)
• [w3c/payment-request] PaymentMethodData should be converted at construction time (#813) (Monday, 26 November)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Monday, 26 November)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Monday, 26 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) (Friday, 23 November)
• Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) (Friday, 23 November)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Friday, 23 November)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Friday, 23 November)
• Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Friday, 23 November)
• [w3c/payment-request] fix: convert PaymentMethodData.data (#812) (Friday, 23 November)
• Re: [w3c/payment-method-basic-card] Add "store" card support (#46) (Thursday, 22 November)
• Re: [w3c/payment-method-basic-card] Add "store" card support (#46) (Thursday, 22 November)
• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) (Thursday, 22 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Thursday, 22 November)
• Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) (Thursday, 22 November)
• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) (Thursday, 22 November)
• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) (Thursday, 22 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Wednesday, 21 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Wednesday, 21 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Wednesday, 21 November)
• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) (Wednesday, 21 November)
• [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) (Wednesday, 21 November)
• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) (Wednesday, 21 November)
• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) (Wednesday, 21 November)
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) (Wednesday, 21 November)
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) (Wednesday, 21 November)
• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) (Wednesday, 21 November)
• Re: [w3c/payment-method-basic-card] Broken link basiccardresponse-member-formats-manual.https.html (#48) (Wednesday, 21 November)
• Re: [w3c/payment-method-basic-card] Broken link basiccardresponse-member-formats-manual.https.html (#48) (Wednesday, 21 November)
• Re: [w3c/payment-method-basic-card] Inconsistent naming of algorithms (#55) (Wednesday, 21 November)
• Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) (Wednesday, 21 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Wednesday, 21 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) (Wednesday, 21 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Wednesday, 21 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Wednesday, 21 November)
• [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Wednesday, 21 November)
• Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) (Wednesday, 21 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) (Wednesday, 21 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) (Tuesday, 20 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) (Tuesday, 20 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) (Tuesday, 20 November)
• [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) (Tuesday, 20 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) (Tuesday, 20 November)
• Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) (Tuesday, 20 November)
• Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) (Monday, 19 November)
• Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) (Monday, 19 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) (Monday, 19 November)
• [w3c/payment-request] Rethink "payment request is showing" boolean (#809) (Monday, 19 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) (Monday, 19 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) (Monday, 19 November)
• Re: [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795) (Monday, 19 November)
• Re: [w3c/payment-request] fix: while retrying complete() returns a rejected promise (#808) (Monday, 19 November)
• [w3c/payment-request] fix: while retrying complete() returns a rejected promise (#808) (Monday, 19 November)
• Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) (Monday, 19 November)
• Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) (Thursday, 15 November)
• [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) (Thursday, 15 November)
• Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) (Thursday, 15 November)
• Re: [w3c/payment-method-basic-card] Drop supportedTypes? (#59) (Thursday, 15 November)
• Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) (Thursday, 15 November)
• Re: [w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64) (Thursday, 15 November)
• Re: [w3c/payment-request] Added section and paragraph on accessibility considerations (#802) (Wednesday, 14 November)
• Re: [w3c/payment-request] Follow up on APA Comments on Web Payments FPWDs (#735) (Wednesday, 14 November)
• Re: [w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64) (Wednesday, 14 November)
• Re: [w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64) (Wednesday, 14 November)
• Re: [w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64) (Wednesday, 14 November)
• Re: [w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64) (Wednesday, 14 November)
• Re: [w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64) (Wednesday, 14 November)
• Re: [w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64) (Wednesday, 14 November)
• [w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64) (Wednesday, 14 November)
• Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) (Wednesday, 14 November)
• Re: [w3c/payment-method-basic-card] Fixed wrong interface name, links and grammatical errors (#63) (Wednesday, 14 November)
• Re: [w3c/payment-method-basic-card] Fixed wrong interface name, links and grammatical errors (#63) (Wednesday, 14 November)
• Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) (Wednesday, 14 November)
• Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) (Wednesday, 14 November)
• Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) (Wednesday, 14 November)
• Re: [w3c/payment-method-basic-card] Fixed wrong interface name, links and grammatical errors (#63) (Tuesday, 13 November)
• Re: [w3c/payment-method-basic-card] Fixed wrong interface name, links and grammatical errors (#63) (Tuesday, 13 November)
• Re: [w3c/payment-method-basic-card] Fixed wrong interface name, links and grammatical errors (#63) (Tuesday, 13 November)
• Re: [w3c/payment-method-basic-card] Fixed wrong interface name, links and grammatical errors (#63) (Tuesday, 13 November)
• Re: [w3c/payment-request] Change what canMakePayment() means (#806) (Saturday, 10 November)
• Re: [w3c/payment-request] Meaning of canMakePayment() (#800) (Saturday, 10 November)
• Re: [w3c/payment-request] Treat scroll as a user gesture for PaymentRequest.show() (#797) (Tuesday, 6 November)
• Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) (Tuesday, 6 November)
• Re: [w3c/payment-request] Way of detecting if can make payment with some instrument (#801) (Tuesday, 6 November)
• Re: [w3c/payment-request] Change what canMakePayment() means (#806) (Monday, 5 November)
• Re: [w3c/payment-request] Change what canMakePayment() means (#806) (Monday, 5 November)
• Re: [w3c/payment-request] Change what canMakePayment() means (#806) (Monday, 5 November)
• Re: [w3c/payment-request] Change what canMakePayment() means (#806) (Monday, 5 November)
• Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) (Monday, 5 November)
• Re: [w3c/payment-request] Change what canMakePayment() means (#806) (Monday, 5 November)
• Re: [w3c/payment-request] Change what canMakePayment() means (#806) (Monday, 5 November)
• [w3c/payment-request] Change what canMakePayment() means (#806) (Monday, 5 November)
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) (Monday, 5 November)
• Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) (Monday, 5 November)
• Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) (Monday, 5 November)
• Re: [w3c/payment-request] fix: retry()'s errorFields should be optional per WebIDL (#805) (Monday, 5 November)
• Re: [w3c/payment-request] fix: retry()'s errorFields should be optional per WebIDL (#805) (Monday, 5 November)
• Re: [w3c/payment-request] fix: retry()'s errorFields should be optional per WebIDL (#805) (Monday, 5 November)
• Re: [w3c/payment-request] retry(errorFields) should be optional (#804) (Monday, 5 November)
• Re: [w3c/payment-method-basic-card] Drop supportedTypes? (#59) (Sunday, 4 November)
• Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) (Thursday, 1 November)
• [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) (Thursday, 1 November)
• Re: [w3c/payment-request] fix: retry()'s errorFields should be optional per WebIDL (#805) (Thursday, 1 November)
• Re: [w3c/payment-request] fix: retry()'s errorFields should be optional per WebIDL (#805) (Thursday, 1 November)
• [w3c/payment-request] fix: retry()'s should be optional per WebIDL (#805) (Thursday, 1 November)
• [w3c/payment-request] retry(errorFields) should be optional (#804) (Thursday, 1 November)

Matt N.

• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) (Thursday, 29 November)
• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) (Wednesday, 21 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) (Wednesday, 21 November)
• Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) (Monday, 19 November)

Michael Cooper

• Re: [w3c/payment-request] Added section and paragraph on accessibility considerations (#802) (Wednesday, 14 November)

Rouslan Solomakhin

• Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) (Thursday, 29 November)
• Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) (Wednesday, 28 November)
• Re: [w3c/payment-request] Include payment handler information in response (#815) (Tuesday, 27 November)
• Re: [w3c/payment-request] Support requesting billing address (#749) (Tuesday, 27 November)
• Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) (Tuesday, 27 November)
• Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) (Monday, 26 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Wednesday, 21 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Wednesday, 21 November)
• Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) (Wednesday, 21 November)
• Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) (Monday, 19 November)
• Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) (Monday, 19 November)
• Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) (Monday, 19 November)
• Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) (Wednesday, 14 November)
• Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) (Tuesday, 13 November)
• Re: [w3c/payment-request] Consider specifying a testing IDL for a mock payment UI (#799) (Tuesday, 13 November)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Tuesday, 6 November)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Tuesday, 6 November)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Tuesday, 6 November)
• Re: [w3c/payment-request] Change what canMakePayment() means (#806) (Monday, 5 November)
• Re: [w3c/payment-request] Change what canMakePayment() means (#806) (Monday, 5 November)
• Re: [w3c/payment-request] Change what canMakePayment() means (#806) (Monday, 5 November)
• Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) (Thursday, 1 November)

Wonsuk Lee

• Re: [w3c/payment-method-basic-card] Fixed wrong interface name, links and grammatical errors (#63) (Tuesday, 13 November)
• Re: [w3c/payment-method-basic-card] Fixed wrong interface name, links and grammatical errors (#63) (Tuesday, 13 November)
• Re: [w3c/payment-method-basic-card] Fixed wrong interface name, links and grammatical errors (#63) (Tuesday, 13 November)
• Re: [w3c/payment-method-basic-card] Fixed wrong interface name, links and grammatical errors (#63) (Tuesday, 13 November)
• [w3c/payment-method-basic-card] Fixed wrong interface name, links and grammatical errors (#63) (Tuesday, 13 November)

Zouhir ⚡️

• Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) (Wednesday, 28 November)
• Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) (Monday, 26 November)
• Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) (Sunday, 4 November)

Last message date: Thursday, 29 November 2018 22:29:06 UTC