public-webpayments-specs@w3.org from August 2016 by author

adamroach

Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Wednesday, 31 August)
Re: [w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11) (Thursday, 18 August)
Re: [w3c/webpayments-methods-card] Add privacy and security section (#8) (Wednesday, 17 August)
[w3c/webpayments-methods-card] Add privacy and security section (#8) (Wednesday, 17 August)
Re: [w3c/webpayments-payment-apps-api] Require secure contexts for web-based payment apps (#24) (Wednesday, 17 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Wednesday, 17 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Wednesday, 17 August)
Re: [w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11) (Tuesday, 16 August)
[w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-payment-apps-api] Communication between JS PaymentApps and the User Agent (#26) (Tuesday, 16 August)
Re: [w3c/webpayments-payment-apps-api] Updates from Tommy's feedback (#28) (Tuesday, 16 August)
[w3c/webpayments-payment-apps-api] Updates from Tommy's feedback (#28) (Tuesday, 16 August)
Re: [w3c/webpayments-payment-apps-api] Communication between JS PaymentApps and the User Agent (#26) (Monday, 15 August)
[w3c/webpayments-payment-apps-api] High-level proposal for general shape of JS API (#25) (Friday, 12 August)
Re: [w3c/webpayments-method-identifiers] Add Security Considerations and Privacy Considerations sections (#7) (Thursday, 11 August)
[w3c/browser-payment-api] Add security text regarding payment apps and phishing (#233) (Wednesday, 10 August)
[w3c/webpayments-payment-apps-api] Require secure contexts for web-based payment apps (#24) (Wednesday, 10 August)
[w3c/browser-payment-api] Clarify that HTTPS is required to use the API (#232) (Wednesday, 10 August)
[w3c/browser-payment-api] Expand Security Considerations Section (#231) (Wednesday, 10 August)
[w3c/webpayments-methods-card] Add Security Considerations and Privacy Considerations sections (#6) (Wednesday, 10 August)
[w3c/webpayments-method-identifiers] Add Security Considerations and Privacy Considerations sections (#7) (Wednesday, 10 August)
[w3c/browser-payment-api] Add Guidance Text for Incognito Mode (#230) (Wednesday, 10 August)
[w3c/webpayments-payment-apps-api] Analyse security properties of payment app execution environment (#23) (Wednesday, 10 August)
Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) (Wednesday, 10 August)
[w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Wednesday, 10 August)
[w3c/webpayments-methods-card] Leave Off Unneeded Information (#5) (Wednesday, 10 August)
Re: [w3c/webpayments-methods-card] Storing card information (#2) (Wednesday, 10 August)
[w3c/browser-payment-api] Expand Privacy Considerations Section (#228) (Wednesday, 10 August)

Ade Bateman

Re: [w3c/browser-payment-api] "Incognito mode" notes (#238) (Tuesday, 30 August)

Adrian Hope-Bailie

Re: [w3c/browser-payment-api] "Incognito mode" notes (#238) (Tuesday, 30 August)
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Monday, 29 August)
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Monday, 29 August)
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Monday, 29 August)
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Saturday, 27 August)
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Friday, 26 August)
Re: [w3c/webpayments-payment-apps-api] Two origin-related additions (#32) (Thursday, 25 August)
Re: [w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11) (Friday, 19 August)
Re: [w3c/webpayments-method-identifiers] Should a payment method identifier that is a URL bind that payment method to a single payment app or origin? (#12) (Friday, 19 August)
Re: [w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11) (Thursday, 18 August)
Re: [w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11) (Thursday, 18 August)
Re: [w3c/webpayments-method-identifiers] Should a payment method identifier that is a URL bind that payment method to a single payment app or origin? (#12) (Thursday, 18 August)
Re: [w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11) (Thursday, 18 August)
[w3c/webpayments-method-identifiers] Should a payment method identifier that is a URL bind that payment method to a single payment app or origin? (#12) (Thursday, 18 August)
Re: [w3c/webpayments-payment-apps-api] Add "incognito mode" text (#31) (Wednesday, 17 August)
Re: [w3c/webpayments-methods-card] Add privacy and security considerations (#7) (Wednesday, 17 August)
Re: [w3c/webpayments-payment-apps-api] Note on usability/security tension around registration (#30) (Wednesday, 17 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Wednesday, 17 August)
Re: [w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11) (Wednesday, 17 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Wednesday, 17 August)
Re: [w3c/webpayments-payment-apps-api] Extending invocation of payment apps with other techniques than HTTP (#10) (Monday, 15 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Monday, 15 August)
Re: [w3c/webpayments-payment-apps-api] High-level proposal for general shape of JS API (#25) (Monday, 15 August)
Re: [w3c/webpayments-payment-apps-api] Remove accepted payment app concept (#22) (Friday, 12 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Friday, 12 August)
Re: [w3c/browser-payment-api] Change “MUST…to be valid” to just “are required” (#236) (Friday, 12 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Friday, 12 August)
Re: [w3c/webpayments-method-identifiers] Add Security Considerations and Privacy Considerations sections (#7) (Friday, 12 August)
Re: [w3c/webpayments-payment-apps-api] Extending invocation of payment apps with other techniques than HTTP (#10) (Tuesday, 9 August)
Re: [w3c/webpayments-payment-apps-api] Extending invocation of payment apps with other techniques than HTTP (#10) (Tuesday, 9 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Tuesday, 9 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Tuesday, 9 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Monday, 8 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Monday, 8 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Monday, 8 August)
Re: [w3c/browser-payment-api] Supporting push payment methods (#224) (Monday, 8 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Monday, 8 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Monday, 8 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Monday, 8 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Monday, 8 August)
[w3c/webpayments-payment-apps-api] Should payment instrument details be included at registration? (#12) (Monday, 1 August)
[w3c/webpayments-payment-apps-api] Should the browser pass user data it has collected (email etc) to the payment app? (#13) (Monday, 1 August)
[w3c/webpayments-payment-apps-api] How can we optimize user experience when there is only one match? (#14) (Monday, 1 August)
[w3c/webpayments-payment-apps-api] Extending invocation of payment apps with other techniques than HTTP (#10) (Monday, 1 August)
[w3c/webpayments-payment-apps-api] What should be the user experience when an app is recommended for two methods? (#11) (Monday, 1 August)
[w3c/webpayments-payment-apps-api] “Security Error” on different origins (#9) (Monday, 1 August)

Andrew Farmer

[w3c/browser-payment-api] Should the API support field validation? (#225) (Monday, 8 August)

Anne van Kesteren

Re: [w3c/browser-payment-api] Clarify that HTTPS is required to use the API (#232) (Wednesday, 24 August)
Re: [w3c/browser-payment-api] Cannot use 2119 terms in notes (#240) (Wednesday, 24 August)
[w3c/browser-payment-api] Annotate all interfaces with SecureContext (#241) (Wednesday, 24 August)
Re: [w3c/browser-payment-api] Clarify that HTTPS is required to use the API (#232) (Wednesday, 24 August)
Re: [w3c/browser-payment-api] Clear pointer to GitHub at the top (#239) (Wednesday, 24 August)
Re: [w3c/browser-payment-api] Clear pointer to GitHub at the top (#239) (Wednesday, 24 August)
[w3c/browser-payment-api] Cannot use 2119 terms in notes (#240) (Wednesday, 24 August)
[w3c/browser-payment-api] Clear pointer to GitHub at the top (#239) (Wednesday, 24 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Wednesday, 17 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Wednesday, 17 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Friday, 12 August)
[w3c/webpayments-method-identifiers] Why URLs? (#9) (Thursday, 11 August)
[w3c/webpayments-method-identifiers] Identifier equivalence does not handle failure (#8) (Thursday, 11 August)
Re: [w3c/webpayments-method-identifiers] Add Security Considerations and Privacy Considerations sections (#7) (Thursday, 11 August)

Arthur Chow

Re: [w3c/browser-payment-api] If a card payment fails, should we support exclusion of that card instrument from matching? (#237) (Tuesday, 23 August)

Dave Longley

Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Saturday, 27 August)
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Saturday, 27 August)
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Saturday, 27 August)
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Saturday, 27 August)
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Friday, 26 August)
Re: [w3c/browser-payment-api] an event to providing standards for push payment methods (#223) (Thursday, 25 August)
Re: [w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11) (Friday, 19 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)

Domenic Denicola

Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Saturday, 27 August)

ianbjacobs

[w3c/webpayments-methods-card] Editorial suggestions (#9) (Friday, 26 August)
Re: [w3c/webpayments-payment-apps-api] Two origin-related additions (#32) (Thursday, 25 August)
Re: [w3c/browser-payment-api] Should the messages support field-level encryption? (#55) (Wednesday, 24 August)
[w3c/webpayments-payment-apps-api] Two origin-related additions (#32) (Wednesday, 24 August)
Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) (Wednesday, 24 August)
Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) (Wednesday, 24 August)
Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) (Monday, 22 August)
Re: [w3c/webpayments-methods-card] Storing card information (#2) (Monday, 22 August)
Re: [w3c/webpayments-payment-apps-api] Add "incognito mode" text (#31) (Wednesday, 17 August)
Re: [w3c/webpayments-methods-card] Add privacy and security considerations (#7) (Wednesday, 17 August)
[w3c/webpayments-payment-apps-api] Add "incognito mode" text (#31) (Wednesday, 17 August)
[w3c/browser-payment-api] "Incognito mode" notes (#238) (Wednesday, 17 August)
Re: [w3c/webpayments-payment-apps-api] Require secure contexts for web-based payment apps (#24) (Wednesday, 17 August)
[w3c/webpayments-methods-card] Add privacy and security considerations (#7) (Wednesday, 17 August)
Re: [w3c/webpayments-payment-apps-api] Note on usability/security tension around registration (#30) (Wednesday, 17 August)
Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) (Wednesday, 17 August)
[w3c/webpayments-payment-apps-api] Note on usability/security tension around registration (#30) (Wednesday, 17 August)
[w3c/webpayments-payment-apps-api] Add issue 127 mention (#29) (Tuesday, 16 August)
Re: [w3c/webpayments-payment-apps-api] Add issue 127 mention (#29) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Monday, 15 August)
[w3c/browser-payment-api] If a card payment fails, should we support exclusion of that card instrument from matching? (#237) (Monday, 15 August)
[w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) (Monday, 15 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Monday, 15 August)
Re: [w3c/webpayments-payment-apps-api] Is the concept of payment app registration necessary? (#8) (Monday, 15 August)
Re: [w3c/webpayments-payment-apps-api] Is the concept of payment app registration necessary? (#8) (Monday, 15 August)
Re: [w3c/webpayments-payment-apps-api] Remove accepted payment app concept (#22) (Friday, 12 August)
Re: [w3c/webpayments-payment-apps-api] Remove accepted payment app concept (#22) (Wednesday, 10 August)
[w3c/webpayments-payment-apps-api] Remove accepted payment app concept (#22) (Wednesday, 10 August)
Re: [w3c/webpayments-payment-apps-api] Should merchants be able to limit matching to trusted apps? (#1) (Wednesday, 10 August)
Re: [w3c/webpayments-payment-apps-api] Should merchants be able to limit matching to trusted apps? (#1) (Wednesday, 10 August)
Re: [w3c/webpayments-payment-apps-api] Design considerations for payment app registration: recommended apps, user consent, and optional registration (#21) (Tuesday, 9 August)
Re: [w3c/webpayments-payment-apps-api] Design considerations for payment app registration: recommended apps, user consent, and optional registration (#21) (Tuesday, 9 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Tuesday, 9 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Tuesday, 9 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Tuesday, 9 August)
[w3c/webpayments-payment-apps-api] Should we distinguish the identifier for a payment app from the identifier for the app server that processes payments? (#20) (Tuesday, 9 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Monday, 8 August)
Re: [w3c/browser-payment-api] Supporting push payment methods (#224) (Monday, 8 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Monday, 8 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Monday, 8 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Monday, 8 August)
Re: [w3c/webpayments-payment-apps-api] Markup fixes (#15) (Friday, 5 August)
[w3c/webpayments-payment-apps-api] Markup fixes (#15) (Friday, 5 August)
[w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Friday, 5 August)
Re: [w3c/webpayments-payment-apps-api] Case sensitive doc type (ED) (#18) (Friday, 5 August)
Re: [w3c/webpayments-payment-apps-api] Remove async perhaps to help with rendering (#17) (Friday, 5 August)
[w3c/webpayments-payment-apps-api] Case sensitive doc type (ED) (#18) (Friday, 5 August)
[w3c/webpayments-payment-apps-api] Remove async perhaps to help with rendering (#17) (Friday, 5 August)
Re: [w3c/webpayments-payment-apps-api] Fixes (#16) (Friday, 5 August)
[w3c/webpayments-payment-apps-api] Fixes (#16) (Friday, 5 August)
Re: [w3c/webpayments-payment-apps-api] What should be the user experience when an app is recommended for two methods? (#11) (Friday, 5 August)
Re: [w3c/webpayments-payment-apps-api] How can we optimize user experience when there is only one match? (#14) (Friday, 5 August)
Re: [w3c/webpayments-payment-apps-api] What should be the user experience when an app is recommended for two methods? (#11) (Wednesday, 3 August)
Re: [w3c/webpayments-payment-apps-api] Should the browser pass user data it has collected (email etc) to the payment app? (#13) (Monday, 1 August)

Jake Archibald

Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Wednesday, 31 August)
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Monday, 29 August)
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Monday, 29 August)
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Saturday, 27 August)
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Saturday, 27 August)
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Friday, 26 August)

Jason Normore

Jeff Burdges

Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) (Wednesday, 17 August)

Manu Sporny

Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Monday, 15 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Friday, 12 August)

Marcos Cáceres

Re: [w3c/browser-payment-api] Cannot use 2119 terms in notes (#240) (Friday, 26 August)

Michael[tm] Smith

Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Saturday, 27 August)
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Saturday, 27 August)
[w3c/browser-payment-api] Specify UA requirements if “id” field of PaymentShippingOption is not unique (#243) (Thursday, 25 August)
Re: [w3c/browser-payment-api] Clarify that HTTPS is required to use the API (#232) (Thursday, 25 August)
[w3c/browser-payment-api] Make ISO4217 an informative reference rather than normative (#242) (Wednesday, 24 August)
Re: [w3c/browser-payment-api] Clear pointer to GitHub at the top (#239) (Wednesday, 24 August)
Re: [w3c/browser-payment-api] Clear pointer to GitHub at the top (#239) (Wednesday, 24 August)
Re: [w3c/webpayments-payment-apps-api] Extending invocation of payment apps with other techniques than HTTP (#10) (Monday, 15 August)
[w3c/browser-payment-api] Change “MUST…to be valid” to just “are required” (#236) (Friday, 12 August)
Re: [w3c/webpayments-method-identifiers] Add Security Considerations and Privacy Considerations sections (#7) (Thursday, 11 August)
[w3c/browser-payment-api] Unambiguously specify UA requirements for instances that are not valid (#235) (Thursday, 11 August)
Re: [w3c/browser-payment-api] U (#234) (Thursday, 11 August)
[w3c/browser-payment-api] U (#234) (Thursday, 11 August)
Re: [w3c/webpayments-method-identifiers] Add Security Considerations and Privacy Considerations sections (#7) (Thursday, 11 August)
Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) (Wednesday, 10 August)

Rouslan Solomakhin

Re: [w3c/webpayments-method-identifiers] Should a payment method identifier that is a URL bind that payment method to a single payment app or origin? (#12) (Thursday, 18 August)
Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) (Tuesday, 16 August)
Re: [w3c/browser-payment-api] Should the API support field validation? (#225) (Monday, 8 August)

rvm4

Re: [w3c/browser-payment-api] "Incognito mode" notes (#238) (Monday, 29 August)
Re: [w3c/browser-payment-api] Change “MUST…to be valid” to just “are required” (#236) (Monday, 29 August)
Re: [w3c/browser-payment-api] Add links into Github (#226) (Monday, 29 August)
[w3c/webpayments-method-identifiers] update pmi spec with apen and proprietary payment method identifiers (#10) (Tuesday, 16 August)

Shane McCarron

Re: [w3c/browser-payment-api] Clarify that HTTPS is required to use the API (#232) (Wednesday, 24 August)
Re: [w3c/browser-payment-api] Cannot use 2119 terms in notes (#240) (Wednesday, 24 August)
Re: [w3c/browser-payment-api] Clarify that HTTPS is required to use the API (#232) (Wednesday, 24 August)
Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) (Monday, 22 August)
Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) (Wednesday, 17 August)
Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) (Tuesday, 16 August)
Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) (Monday, 15 August)
Re: [w3c/browser-payment-api] If a card payment fails, should we support exclusion of that card instrument from matching? (#237) (Monday, 15 August)
Re: [w3c/browser-payment-api] Change “MUST…to be valid” to just “are required” (#236) (Friday, 12 August)
[w3c/browser-payment-api] Normative References (#227) (Wednesday, 10 August)
[w3c/browser-payment-api] Add links into Github (#226) (Wednesday, 10 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Sunday, 7 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Sunday, 7 August)
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) (Sunday, 7 August)

Tab Atkins Jr.

Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Wednesday, 17 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Monday, 15 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Monday, 15 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Friday, 12 August)

Tommy Thorsen

Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Monday, 29 August)
[w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Friday, 26 August)
Re: [w3c/webpayments-payment-apps-api] Communication between JS PaymentApps and the User Agent (#26) (Wednesday, 17 August)
Re: [w3c/webpayments-payment-apps-api] Communication between JS PaymentApps and the User Agent (#26) (Wednesday, 17 August)
[w3c/webpayments-payment-apps-api] Communication between JS PaymentApps and the User Agent (#26) (Monday, 15 August)
Re: [w3c/webpayments-payment-apps-api] Extending invocation of payment apps with other techniques than HTTP (#10) (Tuesday, 9 August)
Re: [w3c/webpayments-payment-apps-api] What should be the user experience when an app is recommended for two methods? (#11) (Tuesday, 2 August)

Zach Koch

Re: [w3c/webpayments-methods-card] Storing card information (#2) (Monday, 22 August)
Re: [w3c/webpayments-methods-card] Storing card information (#2) (Friday, 19 August)
Re: [w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11) (Thursday, 18 August)
Re: [w3c/webpayments-method-identifiers] Should a payment method identifier that is a URL bind that payment method to a single payment app or origin? (#12) (Thursday, 18 August)
Re: [w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11) (Thursday, 18 August)
Re: [w3c/webpayments-method-identifiers] Should a payment method identifier that is a URL bind that payment method to a single payment app or origin? (#12) (Thursday, 18 August)
Re: [w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11) (Thursday, 18 August)
Re: [w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 16 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Monday, 15 August)
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Monday, 15 August)

Last message date: Wednesday, 31 August 2016 22:39:30 UTC