- Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Adrian Hope-Bailie (Thursday, 31 March)
- Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Jeff Burdges (Thursday, 31 March)
- Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Adrian Hope-Bailie (Thursday, 31 March)
- Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Jeff Burdges (Thursday, 31 March)
- Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Adrian Hope-Bailie (Thursday, 31 March)
- Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) mattsaxon (Thursday, 31 March)
- Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Zach Koch (Thursday, 31 March)
- Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) mattsaxon (Thursday, 31 March)
- Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Zach Koch (Thursday, 31 March)
- Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) mattsaxon (Thursday, 31 March)
- Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Zach Koch (Thursday, 31 March)
- Re: [w3c/browser-payment-api] Currency amount (#101) Shane McCarron (Tuesday, 29 March)
- Re: [w3c/browser-payment-api] Currency amount (#101) Adrian Hope-Bailie (Tuesday, 29 March)
- Re: [w3c/browser-payment-api] Currency amount (#101) Adrian Hope-Bailie (Tuesday, 29 March)
- Re: [w3c/browser-payment-api] Currency amount (#101) Shane McCarron (Tuesday, 29 March)
- Re: [w3c/browser-payment-api] Currency amount (#101) mattsaxon (Tuesday, 29 March)
- Re: [w3c/browser-payment-api] Currency amount (#101) Adrian Hope-Bailie (Wednesday, 30 March)
- Re: [w3c/browser-payment-api] Currency amount (#101) Adrian Hope-Bailie (Thursday, 31 March)
- Re: [w3c/browser-payment-api] Currency amount (#101) Zach Koch (Thursday, 31 March)
- Re: [w3c/browser-payment-api] Currency amount (#101) kirkalx (Thursday, 31 March)
- Re: [w3c/browser-payment-api] Currency amount (#101) kirkalx (Thursday, 31 March)
- Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) David Illsley (Wednesday, 23 March)
- Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) mattsaxon (Wednesday, 23 March)
- Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Rouslan Solomakhin (Wednesday, 23 March)
- Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Dave Longley (Wednesday, 23 March)
- Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Nick S (Wednesday, 23 March)
- Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Adrian Hope-Bailie (Wednesday, 23 March)
- Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Dave Longley (Wednesday, 23 March)
- Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) mattsaxon (Wednesday, 23 March)
- Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Rouslan Solomakhin (Wednesday, 23 March)
- Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Rouslan Solomakhin (Thursday, 24 March)
- Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Shane McCarron (Thursday, 24 March)
- Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Rouslan Solomakhin (Thursday, 24 March)
- Re: [browser-payment-api] Change the way we request user data (#65) Manu Sporny (Tuesday, 15 March)
- Re: [browser-payment-api] Change the way we request user data (#65) Manu Sporny (Tuesday, 15 March)
- Re: [browser-payment-api] Change the way we request user data (#65) Zach Koch (Tuesday, 15 March)
- Re: [browser-payment-api] Change the way we request user data (#65) Manu Sporny (Tuesday, 15 March)
- Re: [browser-payment-api] Change the way we request user data (#65) Manu Sporny (Tuesday, 15 March)
- Re: [browser-payment-api] Change the way we request user data (#65) ianbjacobs (Tuesday, 15 March)
- Re: [browser-payment-api] Change the way we request user data (#65) Adrian Hope-Bailie (Thursday, 17 March)
- Re: [browser-payment-api] Change the way we request user data (#65) mattsaxon (Sunday, 20 March)
- Re: [browser-payment-api] Change the way we request user data (#65) Adrian Hope-Bailie (Thursday, 24 March)
- Re: [browser-payment-api] Change the way we request user data (#65) Jeff Burdges (Thursday, 24 March)
- Re: [browser-payment-api] Change the way we request user data (#65) Zach Koch (Thursday, 24 March)
- Re: [browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Adrian Hope-Bailie (Monday, 14 March)
- Re: [browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Adrian Hope-Bailie (Monday, 14 March)
- Re: [browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Shane McCarron (Monday, 14 March)
- Re: [browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Nick Telford-Reed (Tuesday, 15 March)
- Re: [browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Rouslan Solomakhin (Wednesday, 23 March)
- Re: [browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) David Illsley (Thursday, 24 March)
- Re: [w3c/browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Matt Saxon (Tuesday, 29 March)
- Re: [w3c/browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) ianbjacobs (Tuesday, 29 March)
- Re: [w3c/browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Adrian Hope-Bailie (Tuesday, 29 March)
- Re: [w3c/browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) ianbjacobs (Tuesday, 29 March)
- Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Ade Bateman (Thursday, 17 March)
- Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Manu Sporny (Thursday, 17 March)
- Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Anders Rundgren (Monday, 21 March)
- Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Rouslan Solomakhin (Wednesday, 23 March)
- Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Anders Rundgren (Friday, 25 March)
- Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Rouslan Solomakhin (Friday, 25 March)
- Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Anders Rundgren (Friday, 25 March)
- Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Anders Rundgren (Friday, 25 March)
- Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Rouslan Solomakhin (Friday, 25 March)
- Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Rouslan Solomakhin (Friday, 25 March)
- Re: [w3c/browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Jeff Burdges (Thursday, 31 March)
- Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) ianbjacobs (Monday, 14 March)
- Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Manu Sporny (Monday, 14 March)
- Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) ianbjacobs (Monday, 14 March)
- Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Dave Longley (Monday, 14 March)
- Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Dave Longley (Monday, 14 March)
- Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Dave Longley (Wednesday, 16 March)
- Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) ianbjacobs (Wednesday, 16 March)
- Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Dave Longley (Wednesday, 16 March)
- Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) ianbjacobs (Wednesday, 16 March)
- Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Dave Longley (Wednesday, 16 March)
- Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) ianbjacobs (Wednesday, 16 March)
- Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Manu Sporny (Wednesday, 16 March)
- Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) ianbjacobs (Thursday, 17 March)
- Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Manu Sporny (Thursday, 17 March)
- Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Shane McCarron (Thursday, 17 March)
- Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) ianbjacobs (Thursday, 17 March)
- Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Manu Sporny (Monday, 14 March)
- Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) ianbjacobs (Monday, 14 March)
- Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) ianbjacobs (Monday, 14 March)
- Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Manu Sporny (Monday, 14 March)
- Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) ianbjacobs (Monday, 14 March)
- Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Manu Sporny (Monday, 14 March)
- Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Ade Bateman (Thursday, 17 March)
- Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Manu Sporny (Thursday, 17 March)
- Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Manu Sporny (Thursday, 17 March)
- Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) ianbjacobs (Thursday, 17 March)
- Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Dave Longley (Thursday, 17 March)
- Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Shane McCarron (Thursday, 17 March)
- Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Adrian Hope-Bailie (Friday, 18 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) ianbjacobs (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) mattsaxon (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Dave Longley (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) ianbjacobs (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Dave Longley (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) ianbjacobs (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Zach Koch (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) ianbjacobs (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Dave Longley (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) ianbjacobs (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Ade Bateman (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) mattsaxon (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Ade Bateman (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Ade Bateman (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Ade Bateman (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) mattsaxon (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) mattsaxon (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) ianbjacobs (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Ade Bateman (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Ade Bateman (Friday, 11 March)
- Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Zach Koch (Wednesday, 16 March)
- Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon (Friday, 11 March)
- Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon (Friday, 11 March)
- Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon (Friday, 11 March)
- Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) Adrian Hope-Bailie (Friday, 11 March)
- Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon (Friday, 11 March)
- Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) Adrian Hope-Bailie (Friday, 11 March)
- Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon (Friday, 11 March)
- Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) Adrian Hope-Bailie (Friday, 11 March)
- Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) Jeff Burdges (Friday, 11 March)
- Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) Adrian Hope-Bailie (Friday, 11 March)
- Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon (Friday, 11 March)
- Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon (Friday, 11 March)
- Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) Ade Bateman (Saturday, 12 March)
- Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) Ade Bateman (Saturday, 12 March)
- Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon (Wednesday, 16 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Ade Bateman (Friday, 11 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Nick S (Saturday, 12 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) mattsaxon (Saturday, 12 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Ade Bateman (Saturday, 12 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Ade Bateman (Saturday, 12 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Nick S (Saturday, 12 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Ade Bateman (Sunday, 13 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) mattsaxon (Sunday, 13 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) dezell (Sunday, 13 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) dezell (Sunday, 13 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Nick S (Sunday, 13 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Zach Koch (Sunday, 13 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Adrian Hope-Bailie (Monday, 21 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) mattsaxon (Monday, 21 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Adrian Hope-Bailie (Wednesday, 23 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Dave Longley (Wednesday, 23 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Adrian Hope-Bailie (Wednesday, 23 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Dave Longley (Wednesday, 23 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Adrian Hope-Bailie (Wednesday, 23 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Rouslan Solomakhin (Wednesday, 23 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Shane McCarron (Thursday, 24 March)
- Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Dave Longley (Thursday, 24 March)
Test new list Ian Jacobs (Thursday, 10 March)
Last message date: Thursday, 31 March 2016 23:55:19 UTC