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

Wednesday, 31 August 2016

Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) Jake Archibald
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) adamroach

Tuesday, 30 August 2016

Re: [w3c/browser-payment-api] "Incognito mode" notes (#238) Ade Bateman
Re: [w3c/browser-payment-api] "Incognito mode" notes (#238) Adrian Hope-Bailie

Monday, 29 August 2016

Saturday, 27 August 2016

Friday, 26 August 2016

Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) Jake Archibald
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) Dave Longley
[w3c/webpayments-methods-card] Editorial suggestions (#9) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) Adrian Hope-Bailie
[w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) Tommy Thorsen
Re: [w3c/browser-payment-api] Cannot use 2119 terms in notes (#240) Marcos Cáceres

Thursday, 25 August 2016

Re: [w3c/webpayments-payment-apps-api] Two origin-related additions (#32) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Two origin-related additions (#32) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] an event to providing standards for push payment methods (#223) Dave Longley
[w3c/browser-payment-api] Specify UA requirements if “id” field of PaymentShippingOption is not unique (#243) Michael[tm] Smith
Re: [w3c/browser-payment-api] Clarify that HTTPS is required to use the API (#232) Michael[tm] Smith

Wednesday, 24 August 2016

Re: [w3c/browser-payment-api] Should the messages support field-level encryption? (#55) ianbjacobs
[w3c/webpayments-payment-apps-api] Two origin-related additions (#32) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) ianbjacobs
Re: [w3c/browser-payment-api] Clarify that HTTPS is required to use the API (#232) Shane McCarron
Re: [w3c/browser-payment-api] Clarify that HTTPS is required to use the API (#232) Anne van Kesteren
Re: [w3c/browser-payment-api] Cannot use 2119 terms in notes (#240) Anne van Kesteren
Re: [w3c/browser-payment-api] Cannot use 2119 terms in notes (#240) Shane McCarron
Re: [w3c/browser-payment-api] Clarify that HTTPS is required to use the API (#232) Shane McCarron
[w3c/browser-payment-api] Make ISO4217 an informative reference rather than normative (#242) Michael[tm] Smith
[w3c/browser-payment-api] Annotate all interfaces with SecureContext (#241) Anne van Kesteren
Re: [w3c/browser-payment-api] Clarify that HTTPS is required to use the API (#232) Anne van Kesteren
Re: [w3c/browser-payment-api] Clear pointer to GitHub at the top (#239) Anne van Kesteren
Re: [w3c/browser-payment-api] Clear pointer to GitHub at the top (#239) Anne van Kesteren
Re: [w3c/browser-payment-api] Clear pointer to GitHub at the top (#239) Michael[tm] Smith
Re: [w3c/browser-payment-api] Clear pointer to GitHub at the top (#239) Michael[tm] Smith
[w3c/browser-payment-api] Cannot use 2119 terms in notes (#240) Anne van Kesteren
[w3c/browser-payment-api] Clear pointer to GitHub at the top (#239) Anne van Kesteren

Tuesday, 23 August 2016

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

Monday, 22 August 2016

Friday, 19 August 2016

Thursday, 18 August 2016

Wednesday, 17 August 2016

Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) Jeff Burdges
Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) Shane McCarron
Re: [w3c/webpayments-payment-apps-api] Add "incognito mode" text (#31) ianbjacobs
Re: [w3c/webpayments-methods-card] Add privacy and security considerations (#7) ianbjacobs
Re: [w3c/webpayments-methods-card] Add privacy and security section (#8) adamroach
[w3c/webpayments-methods-card] Add privacy and security section (#8) adamroach
Re: [w3c/webpayments-payment-apps-api] Require secure contexts for web-based payment apps (#24) adamroach
Re: [w3c/webpayments-payment-apps-api] Add "incognito mode" text (#31) Adrian Hope-Bailie
Re: [w3c/webpayments-methods-card] Add privacy and security considerations (#7) Adrian Hope-Bailie
[w3c/webpayments-payment-apps-api] Add "incognito mode" text (#31) ianbjacobs
[w3c/browser-payment-api] "Incognito mode" notes (#238) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Require secure contexts for web-based payment apps (#24) ianbjacobs
[w3c/webpayments-methods-card] Add privacy and security considerations (#7) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Note on usability/security tension around registration (#30) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Note on usability/security tension around registration (#30) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) ianbjacobs
[w3c/webpayments-payment-apps-api] Note on usability/security tension around registration (#30) ianbjacobs
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) Adrian Hope-Bailie
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) Anne van Kesteren
Re: [w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11) Adrian Hope-Bailie
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) Adrian Hope-Bailie
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) Anne van Kesteren
Re: [w3c/webpayments-payment-apps-api] Communication between JS PaymentApps and the User Agent (#26) Tommy Thorsen
Re: [w3c/webpayments-payment-apps-api] Communication between JS PaymentApps and the User Agent (#26) Tommy Thorsen
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) adamroach
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) Tab Atkins Jr.
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) adamroach

Tuesday, 16 August 2016

Monday, 15 August 2016

Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) Tab Atkins Jr.
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) ianbjacobs
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) Tab Atkins Jr.
Re: [w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) Shane McCarron
Re: [w3c/browser-payment-api] If a card payment fails, should we support exclusion of that card instrument from matching? (#237) Shane McCarron
[w3c/browser-payment-api] If a card payment fails, should we support exclusion of that card instrument from matching? (#237) ianbjacobs
[w3c/webpayments-payment-apps-api] Should origin information (about the payment request) be shared with the payment app? (#27) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Communication between JS PaymentApps and the User Agent (#26) adamroach
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) Zach Koch
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) ianbjacobs
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) Manu Sporny
Re: [w3c/webpayments-payment-apps-api] Is the concept of payment app registration necessary? (#8) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Is the concept of payment app registration necessary? (#8) ianbjacobs
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) Zach Koch
[w3c/webpayments-payment-apps-api] Communication between JS PaymentApps and the User Agent (#26) Tommy Thorsen
Re: [w3c/webpayments-payment-apps-api] Extending invocation of payment apps with other techniques than HTTP (#10) Adrian Hope-Bailie
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] High-level proposal for general shape of JS API (#25) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Extending invocation of payment apps with other techniques than HTTP (#10) Michael[tm] Smith

Friday, 12 August 2016

[w3c/webpayments-payment-apps-api] High-level proposal for general shape of JS API (#25) adamroach
Re: [w3c/browser-payment-api] Change “MUST…to be valid” to just “are required” (#236) Shane McCarron
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) Tab Atkins Jr.
Re: [w3c/webpayments-payment-apps-api] Remove accepted payment app concept (#22) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Remove accepted payment app concept (#22) Adrian Hope-Bailie
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) Manu Sporny
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Change “MUST…to be valid” to just “are required” (#236) Adrian Hope-Bailie
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) Anne van Kesteren
Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) Adrian Hope-Bailie
Re: [w3c/webpayments-method-identifiers] Add Security Considerations and Privacy Considerations sections (#7) Adrian Hope-Bailie
[w3c/browser-payment-api] Change “MUST…to be valid” to just “are required” (#236) Michael[tm] Smith

Thursday, 11 August 2016

[w3c/webpayments-method-identifiers] Why URLs? (#9) Anne van Kesteren
[w3c/webpayments-method-identifiers] Identifier equivalence does not handle failure (#8) Anne van Kesteren
Re: [w3c/webpayments-method-identifiers] Add Security Considerations and Privacy Considerations sections (#7) Anne van Kesteren
Re: [w3c/webpayments-method-identifiers] Add Security Considerations and Privacy Considerations sections (#7) Michael[tm] Smith
Re: [w3c/webpayments-method-identifiers] Add Security Considerations and Privacy Considerations sections (#7) adamroach
[w3c/browser-payment-api] Unambiguously specify UA requirements for instances that are not valid (#235) Michael[tm] Smith
Re: [w3c/browser-payment-api] U (#234) Michael[tm] Smith
[w3c/browser-payment-api] U (#234) Michael[tm] Smith
Re: [w3c/webpayments-method-identifiers] Add Security Considerations and Privacy Considerations sections (#7) Michael[tm] Smith

Wednesday, 10 August 2016

Tuesday, 9 August 2016

Monday, 8 August 2016

[w3c/browser-payment-api] Should the API support field validation? (#225) Andrew Farmer
Re: [w3c/browser-payment-api] Should the API support field validation? (#225) Rouslan Solomakhin
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) ianbjacobs
Re: [w3c/browser-payment-api] Supporting push payment methods (#224) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) ianbjacobs
Re: [w3c/browser-payment-api] Supporting push payment methods (#224) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) Adrian Hope-Bailie

Sunday, 7 August 2016

Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) Shane McCarron
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) Shane McCarron
Re: [w3c/webpayments-payment-apps-api] Addition of new design considerations (#19) Shane McCarron

Friday, 5 August 2016

Wednesday, 3 August 2016

Re: [w3c/webpayments-payment-apps-api] What should be the user experience when an app is recommended for two methods? (#11) ianbjacobs

Tuesday, 2 August 2016

Re: [w3c/webpayments-payment-apps-api] What should be the user experience when an app is recommended for two methods? (#11) Tommy Thorsen

Monday, 1 August 2016

Re: [w3c/webpayments-payment-apps-api] Should the browser pass user data it has collected (email etc) to the payment app? (#13) ianbjacobs
[w3c/webpayments-payment-apps-api] Should payment instrument details be included at registration? (#12) Adrian Hope-Bailie
[w3c/webpayments-payment-apps-api] Should the browser pass user data it has collected (email etc) to the payment app? (#13) Adrian Hope-Bailie
[w3c/webpayments-payment-apps-api] How can we optimize user experience when there is only one match? (#14) Adrian Hope-Bailie
[w3c/webpayments-payment-apps-api] Extending invocation of payment apps with other techniques than HTTP (#10) Adrian Hope-Bailie
[w3c/webpayments-payment-apps-api] What should be the user experience when an app is recommended for two methods? (#11) Adrian Hope-Bailie
[w3c/webpayments-payment-apps-api] “Security Error” on different origins (#9) Adrian Hope-Bailie

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