public-webpayments-specs@w3.org from July 2016 by subject

[w3c/browser-payment-api] add an additional event in the hopes of providing standars for push p… (#223)

• rvm4 (Thursday, 7 July)

[w3c/browser-payment-api] an event to providing standards for push payment methods (#223)

• Adrian Hope-Bailie (Friday, 29 July)
• rvm4 (Thursday, 28 July)
• ianbjacobs (Tuesday, 19 July)
• Adrian Hope-Bailie (Tuesday, 19 July)
• ianbjacobs (Tuesday, 19 July)
• Adrian Hope-Bailie (Tuesday, 19 July)
• ianbjacobs (Monday, 18 July)

[w3c/browser-payment-api] Currency Types and Rendering (#185)

• ianbjacobs (Monday, 18 July)
• ianbjacobs (Monday, 18 July)
• Adrian Hope-Bailie (Thursday, 7 July)
• Adrian Hope-Bailie (Thursday, 7 July)

[w3c/browser-payment-api] Fix a minor typo in PaymentRequest constructor description. (#221)

• Ade Bateman (Tuesday, 5 July)

[w3c/browser-payment-api] Removing notes for closed issues. (#222)

• Zach Koch (Friday, 8 July)
• Ade Bateman (Thursday, 7 July)

[w3c/browser-payment-api] Supporting push payment methods (#224)

• mattsaxon (Friday, 29 July)
• rvm4 (Thursday, 28 July)
• Adrian Hope-Bailie (Tuesday, 12 July)
• rvm4 (Tuesday, 12 July)
• rvm4 (Friday, 8 July)
• Adrian Hope-Bailie (Friday, 8 July)
• rvm4 (Friday, 8 July)
• Adrian Hope-Bailie (Thursday, 7 July)
• rvm4 (Thursday, 7 July)

[w3c/webpayments-method-identifiers] slight rewording (#6)

• Erik Wilde (Tuesday, 5 July)

[w3c/webpayments-method-identifiers] Update references and issue markers (#4)

• Ade Bateman (Friday, 1 July)

[w3c/webpayments-payment-apps-api] Display may be subject to user and local policy (consider UA making security decisions etc) (#5)

• Adrian Hope-Bailie (Wednesday, 20 July)

[w3c/webpayments-payment-apps-api] Is the concept of payment app registration necessary? (#8)

• Shane McCarron (Thursday, 28 July)
• Michael[tm] Smith (Thursday, 28 July)
• Shane McCarron (Thursday, 28 July)
• Michael[tm] Smith (Thursday, 28 July)
• Michael[tm] Smith (Thursday, 28 July)
• ianbjacobs (Thursday, 28 July)
• Tommy Thorsen (Thursday, 28 July)
• Adrian Hope-Bailie (Thursday, 28 July)
• ianbjacobs (Wednesday, 27 July)
• Shane McCarron (Wednesday, 27 July)
• ianbjacobs (Wednesday, 27 July)
• Shane McCarron (Wednesday, 27 July)
• ianbjacobs (Wednesday, 27 July)
• ianbjacobs (Thursday, 21 July)
• Jason Normore (Wednesday, 20 July)
• Manu Sporny (Wednesday, 20 July)
• Jason Normore (Wednesday, 20 July)
• Manu Sporny (Wednesday, 20 July)
• Jason Normore (Wednesday, 20 July)
• Manu Sporny (Wednesday, 20 July)
• Jason Normore (Wednesday, 20 July)

[w3c/webpayments-payment-apps-api] PROPOSAL: Payment Apps are javascript code that use event listeners to get the PaymentRequest (#3)

• Adrian Hope-Bailie (Wednesday, 20 July)
• Adrian Hope-Bailie (Wednesday, 20 July)
• Adrian Hope-Bailie (Wednesday, 20 July)

[w3c/webpayments-payment-apps-api] Should merchants be able to limit matching to trusted apps? (#1)

• Adrian Hope-Bailie (Wednesday, 20 July)

[w3c/webpayments-payment-apps-api] Should we allow payment providers to issue queries about their installed payment apps (match on origin) (#6)

• Adrian Hope-Bailie (Wednesday, 20 July)

[w3c/webpayments-payment-apps-api] Split out enabled and supported methods (#7)

• Adrian Hope-Bailie (Wednesday, 20 July)

[w3c/webpayments-payment-apps-api] What is the process for rendering the payment app UI (#4)

• Adrian Hope-Bailie (Wednesday, 20 July)

[w3c/webpayments-payment-apps-api] What portion of the PaymentRequest is sent to the payment app? (#2)

• Adrian Hope-Bailie (Thursday, 28 July)
• ianbjacobs (Wednesday, 20 July)
• Adrian Hope-Bailie (Wednesday, 20 July)

Last message date: Friday, 29 July 2016 11:26:59 UTC