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

Thursday, 29 November 2018

Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) Marcos Cáceres
Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) Marcos Cáceres
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Domenic Denicola
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Domenic Denicola
Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) Matt N.
Re: [w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) Rouslan Solomakhin
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
[w3c/payment-request] Should we put `regionCode` attribute at risk? (#816) Marcos Cáceres
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres

Wednesday, 28 November 2018

Re: [w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792) Marcos Cáceres
Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Marcos Cáceres
Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) Zouhir ⚡️
Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) Rouslan Solomakhin
Re: [w3c/payment-request] Support requesting billing address (#749) Marcos Cáceres
Re: [w3c/payment-request] Support requesting billing address (#749) Christos Constantinou
Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) Marcos Cáceres
Re: [w3c/payment-request] Support requesting billing address (#749) Marcos Cáceres
Re: [w3c/payment-request] Support requesting billing address (#749) Marcos Cáceres
Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) Marcos Cáceres
Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Things needed to publish as note (#43) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Things needed to publish as note (#43) Marcos Cáceres
Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) Marcos Cáceres
Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) Marcos Cáceres
Re: [w3c/payment-request] Support requesting billing address (#749) Marcos Cáceres
Re: [w3c/payment-request] Support requesting billing address (#749) Marcos Cáceres
Re: [w3c/payment-request] Support requesting billing address (#749) Marcos Cáceres
Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) Marcos Cáceres

Tuesday, 27 November 2018

Re: [w3c/payment-request] Include payment handler information in response (#815) Rouslan Solomakhin
Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) ianbjacobs
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) ianbjacobs
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) ianbjacobs
[w3c/payment-request] Include payment handler information in response (#815) ianbjacobs
Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Domenic Denicola
Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) Domenic Denicola
Re: [w3c/payment-request] Support requesting billing address (#749) Christos Constantinou
Re: [w3c/payment-request] Support requesting billing address (#749) Rouslan Solomakhin
Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) Rouslan Solomakhin
Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) Marcos Cáceres
Re: [w3c/payment-request] Treat scroll as a user gesture for PaymentRequest.show() (#797) Marcos Cáceres
Re: [w3c/payment-request] Treat scroll as a user gesture for PaymentRequest.show() (#797) Marcos Cáceres
Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) Marcos Cáceres
Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) Marcos Cáceres
[w3c/payment-request] De-duplicate "user aborts the payment request" and "abort the update (#814) Marcos Cáceres
Re: [w3c/payment-request] fix: while retrying complete() returns a rejected promise (#808) Marcos Cáceres
Re: [w3c/payment-request] fix: while retrying complete() returns a rejected promise (#808) Marcos Cáceres
Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) Marcos Cáceres
Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) aestes
Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) Marcos Cáceres
Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) Marcos Cáceres
Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) Marcos Cáceres
Re: [w3c/payment-request] Support requesting billing address (#749) Marcos Cáceres

Monday, 26 November 2018

Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) aestes
Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) aestes
Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) Zouhir ⚡️
Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) Rouslan Solomakhin
Re: [w3c/payment-request] Should PaymentMethodData be converted at construction time? (#813) Marcos Cáceres
[w3c/payment-request] PaymentMethodData should be converted at construction time (#813) Marcos Cáceres
Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Marcos Cáceres
Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Marcos Cáceres

Friday, 23 November 2018

Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) Marcos Cáceres
Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) Marcos Cáceres
Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Marcos Cáceres
Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Marcos Cáceres
Re: [w3c/payment-request] fix: convert PaymentMethodData.data (#812) Marcos Cáceres
[w3c/payment-request] fix: convert PaymentMethodData.data (#812) Marcos Cáceres

Thursday, 22 November 2018

Re: [w3c/payment-method-basic-card] Add "store" card support (#46) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Add "store" card support (#46) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) Marcos Cáceres
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Redact more things from billingAddress (#65) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) Marcos Cáceres
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Domenic Denicola
Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) Domenic Denicola

Wednesday, 21 November 2018

Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) Matt N.
Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) Matt N.
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Rouslan Solomakhin
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Rouslan Solomakhin
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Rouslan Solomakhin
Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) Marcos Cáceres
[w3c/payment-method-basic-card] Redact more things from billingAddress (#65) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) 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) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Broken link basiccardresponse-member-formats-manual.https.html (#48) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Broken link basiccardresponse-member-formats-manual.https.html (#48) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Inconsistent naming of algorithms (#55) Marcos Cáceres
Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) Marcos Cáceres
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) Marcos Cáceres
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
Re: [w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
[w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811) Marcos Cáceres
Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) Marcos Cáceres
Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) Marcos Cáceres

Tuesday, 20 November 2018

Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) Adrian Hope-Bailie
Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) Domenic Denicola
Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) Marcos Cáceres
Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) Marcos Cáceres
Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) Marcos Cáceres
[w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810) Marcos Cáceres
Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) Marcos Cáceres
Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) Marcos Cáceres
Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) ianbjacobs

Monday, 19 November 2018

Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) Marcos Cáceres
Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) ianbjacobs
Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) Matt N.
Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) aestes
Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) Adrian Hope-Bailie
Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) Rouslan Solomakhin
Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) Rouslan Solomakhin
Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) Rouslan Solomakhin
Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) Marcos Cáceres
Re: [w3c/payment-request] Rethink "payment request is showing" boolean (#809) ianbjacobs
Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) Adrian Hope-Bailie
Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) Marcos Cáceres
[w3c/payment-request] Rethink "payment request is showing" boolean (#809) Marcos Cáceres
Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) Marcos Cáceres
Re: [w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796) Marcos Cáceres
Re: [w3c/payment-request] Clarify the behavior of calling PaymentResponse.complete() while [[retryPromise]] is pending (#795) Marcos Cáceres
Re: [w3c/payment-request] fix: while retrying complete() returns a rejected promise (#808) Marcos Cáceres
[w3c/payment-request] fix: while retrying complete() returns a rejected promise (#808) Marcos Cáceres
Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) Marcos Cáceres

Thursday, 15 November 2018

Re: [w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) Marcos Cáceres
[w3c/payment-request] Warn when errorFields don't match request[[options]] (#807) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Drop supportedTypes? (#59) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) Marcos Cáceres
Re: [w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64) Marcos Cáceres

Wednesday, 14 November 2018

Re: [w3c/payment-request] Added section and paragraph on accessibility considerations (#802) Marcos Cáceres
Re: [w3c/payment-request] Follow up on APA Comments on Web Payments FPWDs (#735) Marcos Cáceres
Re: [w3c/payment-request] Added section and paragraph on accessibility considerations (#802) Michael Cooper
Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) Rouslan Solomakhin
Re: [w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64) Marcos Cáceres
Re: [w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64) Marcos Cáceres
Re: [w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64) Marcos Cáceres
Re: [w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64) Marcos Cáceres
Re: [w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64) Marcos Cáceres
Re: [w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64) Marcos Cáceres
[w3c/payment-method-basic-card] chore(.travis.yml): enable ReSpec validation (#64) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Fixed wrong interface name, links and grammatical errors (#63) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Fixed wrong interface name, links and grammatical errors (#63) Marcos Cáceres
Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) Marcos Cáceres
Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) Marcos Cáceres
Re: [w3c/payment-handler] Cross-origin iframes and feature policy. (#282) Marcos Cáceres

Tuesday, 13 November 2018

Monday, 12 November 2018

[w3c/webpayments-methods-tokenization] Should tokenization be a URL-based payment method? (#54) ianbjacobs

Saturday, 10 November 2018

Re: [w3c/payment-request] Change what canMakePayment() means (#806) Marcos Cáceres
Re: [w3c/payment-request] Meaning of canMakePayment() (#800) Marcos Cáceres

Friday, 9 November 2018

Re: [w3c/payment-request] Meaning of canMakePayment() (#800) Jenan Wise
Re: [w3c/payment-request] Change what canMakePayment() means (#806) Domenic Denicola

Wednesday, 7 November 2018

Tuesday, 6 November 2018

Monday, 5 November 2018

Re: [w3c/payment-request] Change what canMakePayment() means (#806) Marcos Cáceres
Re: [w3c/payment-request] Change what canMakePayment() means (#806) Marcos Cáceres
Re: [w3c/payment-request] Change what canMakePayment() means (#806) Rouslan Solomakhin
Re: [w3c/payment-request] Change what canMakePayment() means (#806) Marcos Cáceres
Re: [w3c/payment-request] Change what canMakePayment() means (#806) Rouslan Solomakhin
Re: [w3c/payment-request] Change what canMakePayment() means (#806) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) ianbjacobs
Re: [w3c/payment-request] Change what canMakePayment() means (#806) Rouslan Solomakhin
Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) ianbjacobs
Re: [w3c/payment-request] Change what canMakePayment() means (#806) Marcos Cáceres
Re: [w3c/payment-request] Change what canMakePayment() means (#806) Marcos Cáceres
[w3c/payment-request] Change what canMakePayment() means (#806) Marcos Cáceres
Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) Marcos Cáceres
Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) Jinho Bang
Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) Jinho Bang
Re: [w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724) Marcos Cáceres
Re: [w3c/payment-request] fix: retry()'s errorFields should be optional per WebIDL (#805) Marcos Cáceres
Re: [w3c/payment-request] fix: retry()'s errorFields should be optional per WebIDL (#805) Marcos Cáceres
Re: [w3c/payment-request] fix: retry()'s errorFields should be optional per WebIDL (#805) Marcos Cáceres
Re: [w3c/payment-request] retry(errorFields) should be optional (#804) Marcos Cáceres

Sunday, 4 November 2018

Re: [w3c/payment-method-basic-card] Drop supportedTypes? (#59) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) Zouhir ⚡️

Friday, 2 November 2018

Thursday, 1 November 2018

Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) Rouslan Solomakhin
Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) Marcos Cáceres
Re: [w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) ianbjacobs
[w3c/payment-method-basic-card] Remove concept of types, supportedTypes, BasicCardType enum (#62) Marcos Cáceres
Re: [w3c/payment-request] fix: retry()'s errorFields should be optional per WebIDL (#805) Marcos Cáceres
Re: [w3c/payment-request] fix: retry()'s errorFields should be optional per WebIDL (#805) Marcos Cáceres
Re: [w3c/payment-request] fix: retry()'s should be optional per WebIDL (#805) Jinho Bang
[w3c/payment-request] fix: retry()'s should be optional per WebIDL (#805) Marcos Cáceres
[w3c/payment-request] retry(errorFields) should be optional (#804) Marcos Cáceres

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