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

Tuesday, 31 May 2016

Re: [w3c/browser-payment-api] PROPOSAL: Payment Method Identifiers taking advantage of URL characteristics (#205) Michael[tm] Smith
Re: [w3c/browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Jason Normore
Re: [w3c/browser-payment-api] Should a payment method identifier (URL) resolve to a machine readable resource that describes it? (#46) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should a payment method identifier (URL) resolve to a machine readable resource that describes it? (#46) Adrian Hope-Bailie
[w3c/browser-payment-api] Move PMI and Card specs out of repo (#207) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] PROPOSAL: Payment Method Identifiers taking advantage of URL characteristics (#205) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] PROPOSAL: Payment Method Identifiers taking advantage of URL characteristics (#205) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should well-known identifiers be used for ubiquitous payment methods (#10) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should well-known identifiers be used for ubiquitous payment methods (#10) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should we define nesting/grouping semantics for payment method identifier matching? (#30) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should we define nesting/grouping semantics for payment method identifier matching? (#30) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] General Comment on Registry Design (#148) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] General Comment on Registry Design (#148) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Registry Access/Handling Registry Change (#151) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Registry Access/Handling Registry Change (#151) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Terminology across all Web Payments documents should be aligned (#43) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Terminology across all Web Payments documents should be aligned (#43) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Storing card information (#199) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Storing card information (#199) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] [basic] Reference trademarks (#94) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] [basic] Reference trademarks (#94) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Specification to include Flow Diagram (#32) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Specification to include Flow Diagram (#32) Adrian Hope-Bailie

Monday, 30 May 2016

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

Saturday, 28 May 2016

Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Adrian Hope-Bailie

Friday, 27 May 2016

Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) ianbjacobs
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Dynamic Currency Conversion (DCC) Support (#178) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) ianbjacobs
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Dynamic Currency Conversion (DCC) Support (#178) Richard Love
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Tommy Thorsen
Re: [w3c/browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Tommy Thorsen
Re: [w3c/browser-payment-api] Dynamic Currency Conversion (DCC) Support (#178) fredMeignien

Thursday, 26 May 2016

Wednesday, 25 May 2016

Tuesday, 24 May 2016

Re: [w3c/browser-payment-api] Should well-known identifiers be used for ubiquitous payment methods (#10) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the API handle pre-auth, recurring payments, and similar scenarios (#19) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the API handle pre-auth, recurring payments, and similar scenarios (#19) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Update promise rejection (#187) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] PROPOSAL: Payment Method Identifiers taking advantage of URL characteristics (#205) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] PROPOSAL: Payment Method Identifiers taking advantage of URL characteristics (#205) Michael[tm] Smith
Re: [w3c/browser-payment-api] Should PaymentItems have a type? (#163) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] PROPOSAL: Payment Method Identifiers taking advantage of URL characteristics (#205) Michael[tm] Smith
Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Concern on Payment Method Identifier requirement (#200) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Concern on Payment Method Identifier requirement (#200) Adrian Hope-Bailie
[w3c/browser-payment-api] PROPOSAL: Payment Method Identifiers taking advantage of URL characteristics (#205) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the amount be in decimal or cents? (#204) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the amount be in decimal or cents? (#204) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Why another API? (#203) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192) Jeff Burdges

Monday, 23 May 2016

Re: [w3c/browser-payment-api] API flow (#177) fredMeignien
Re: [w3c/browser-payment-api] Why another API? (#203) Adrian Hope-Bailie

Sunday, 22 May 2016

Re: [w3c/browser-payment-api] Why another API? (#203) Thomas Jensen
Re: [w3c/browser-payment-api] Should the amount be in decimal or cents? (#204) Dave Longley
Re: [w3c/browser-payment-api] Should the amount be in decimal or cents? (#204) adamroach
Re: [w3c/browser-payment-api] Why another API? (#203) Dave Longley
Re: [w3c/browser-payment-api] Why another API? (#203) Jeff Burdges
Re: [w3c/browser-payment-api] Why another API? (#203) adamroach
Re: [w3c/browser-payment-api] Why another API? (#203) Thomas Jensen
Re: [w3c/browser-payment-api] Should the amount be in decimal or cents? (#204) Rouslan Solomakhin
[w3c/browser-payment-api] Should the amount be in decimal or cents? (#204) Guille Paz
Re: [w3c/browser-payment-api] API flow (#177) fredMeignien

Saturday, 21 May 2016

Re: [w3c/browser-payment-api] Why another API? (#203) Jeff Burdges
Re: [w3c/browser-payment-api] Why another API? (#203) ianbjacobs
Re: [w3c/browser-payment-api] Why another API? (#203) Thomas Jensen
Re: [w3c/browser-payment-api] Why another API? (#203) ianbjacobs
[w3c/browser-payment-api] Why another API? (#203) Thomas Jensen
Re: [w3c/browser-payment-api] Specification of required fields (#114) Rouslan Solomakhin

Friday, 20 May 2016

Re: [w3c/browser-payment-api] Terms and conditions next to "Pay" button (#195) Nick Shearer
[w3c/browser-payment-api] Add missing curly bracket (#202) derekjohnson
[w3c/browser-payment-api] Removing erroneous <svg> clip boundaries (#201) adamroach
Re: [w3c/browser-payment-api] Should well-known identifiers be used for ubiquitous payment methods (#10) Michael[tm] Smith

Thursday, 19 May 2016

Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) ianbjacobs
Re: [w3c/browser-payment-api] Concern on Payment Method Identifier requirement (#200) ianbjacobs
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) adamroach
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) ianbjacobs
Re: [w3c/browser-payment-api] Use navigator.payments singleton, factory method, or PaymentRequest constructor (#16) Ade Bateman
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Dave Longley
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Dave Longley
Re: [w3c/browser-payment-api] ShippingAddress versus Address (#189) Ade Bateman
Re: [w3c/browser-payment-api] Care of (#197) Ade Bateman
Re: [w3c/browser-payment-api] shippingAddress and "c/o" field (#186) Ade Bateman
Re: [w3c/browser-payment-api] Care of (#197) Ade Bateman
Re: [w3c/browser-payment-api] Address alignment (#198) Ade Bateman
Re: [w3c/browser-payment-api] Address alignment (#198) Ade Bateman
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) adamroach
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) ianbjacobs
Re: [w3c/browser-payment-api] Add support for ShippingOption.selected. (#179) Ade Bateman
Re: [w3c/browser-payment-api] Add support for ShippingOption.selected. (#179) Ade Bateman
Re: [w3c/browser-payment-api] Care of (#197) David I. Lehn
Re: [w3c/browser-payment-api] Address alignment (#198) Jason Normore
Re: [w3c/browser-payment-api] Care of (#197) Dave Longley
Re: [w3c/browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) adamroach
Re: [w3c/browser-payment-api] Should we define nesting/grouping semantics for payment method identifier matching? (#30) maoyanhua
Re: [w3c/browser-payment-api] Concern on Payment Method Identifier requirement (#200) maoyanhua
Re: [w3c/browser-payment-api] Should we define nesting/grouping semantics for payment method identifier matching? (#30) adamroach
Re: [w3c/browser-payment-api] Should we define nesting/grouping semantics for payment method identifier matching? (#30) maoyanhua
Re: [w3c/browser-payment-api] Remove delegated state and make abort() return a promise (#190) Ade Bateman
Re: [w3c/browser-payment-api] Remove delegated state and make abort() return a promise (#190) Ade Bateman
Re: [w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Concern on Payment Method Identifier requirement (#200) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Jason Normore
Re: [w3c/browser-payment-api] Storing card information (#199) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Terms and conditions next to "Pay" button (#195) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Use navigator.payments singleton, factory method, or PaymentRequest constructor (#16) Adrian Hope-Bailie

Wednesday, 18 May 2016

Re: [w3c/browser-payment-api] Remove delegated state and make abort() return a promise (#190) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) adamroach
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Dave Longley
Re: [w3c/browser-payment-api] Should well-known identifiers be used for ubiquitous payment methods (#10) Erik Wilde
Re: [w3c/browser-payment-api] Should well-known identifiers be used for ubiquitous payment methods (#10) Erik Wilde
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) adamroach
Re: [w3c/browser-payment-api] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#45) ianbjacobs
Re: [w3c/browser-payment-api] Should well-known identifiers be used for ubiquitous payment methods (#10) Rouslan Solomakhin
Re: [w3c/browser-payment-api] What component does the payment method intersection? (#103) ianbjacobs
Re: [w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) ianbjacobs
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) ianbjacobs
Re: [w3c/browser-payment-api] Should well-known identifiers be used for ubiquitous payment methods (#10) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should PaymentItems have a type? (#163) Adrian Hope-Bailie

Tuesday, 17 May 2016

Re: [w3c/browser-payment-api] Identifiers or Locators (#150) ianbjacobs
Re: [w3c/browser-payment-api] Registry Access/Handling Registry Change (#151) Erik Wilde
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
Re: [w3c/browser-payment-api] Registry Access/Handling Registry Change (#151) ianbjacobs
Re: [w3c/browser-payment-api] Registry Access/Handling Registry Change (#151) Erik Wilde
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) ianbjacobs
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) ianbjacobs
Re: [w3c/browser-payment-api] Registry Access/Handling Registry Change (#151) ianbjacobs
Re: [w3c/browser-payment-api] Address alignment (#198) rvm4
Re: [w3c/browser-payment-api] Should PaymentItems have a type? (#163) rvm4
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) Rouslan Solomakhin
Re: [w3c/browser-payment-api] ShippingAddress versus Address (#189) adamroach
Re: [w3c/browser-payment-api] Rename the address type since it will likely be used for other purposes. (#193) Ade Bateman
Re: [w3c/browser-payment-api] Rename the address type since it will likely be used for other purposes. (#193) Ade Bateman
Re: [w3c/browser-payment-api] Should the payment mediator pass all payment method data to the payment app or just relevant data? (#157) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] API flow (#177) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add support for ShippingOption.selected. (#179) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) ianbjacobs
Re: [w3c/browser-payment-api] Concern on Payment Method Identifier requirement (#200) ianbjacobs
Re: [w3c/browser-payment-api] Visibility of Payment Options (#194) ianbjacobs
Re: [w3c/browser-payment-api] Storing card information (#199) mattsaxon
Re: [w3c/browser-payment-api] Storing card information (#199) Rouslan Solomakhin
Re: [w3c/browser-payment-api] ShippingAddress versus Address (#189) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Terms and conditions next to "Pay" button (#195) Nick Shearer
[w3c/browser-payment-api] Concern on Payment Method Identifier requirement (#200) maoyanhua
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) adamroach
Re: [w3c/browser-payment-api] ShippingAddress versus Address (#189) adamroach
Re: [w3c/browser-payment-api] Storing card information (#199) adamroach
Re: [w3c/browser-payment-api] ShippingAddress versus Address (#189) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Visibility of Payment Options (#194) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Storing card information (#199) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Terms and conditions next to "Pay" button (#195) Rouslan Solomakhin

Monday, 16 May 2016

Re: [w3c/browser-payment-api] Terms and conditions next to "Pay" button (#195) Nick Shearer
Re: [w3c/browser-payment-api] Storing card information (#199) Nick Shearer
[w3c/browser-payment-api] Storing card information (#199) adamroach
[w3c/browser-payment-api] Address alignment (#198) adamroach
[w3c/browser-payment-api] Care of (#197) adamroach
Re: [w3c/browser-payment-api] adding careOf field (#196) adamroach
Re: [w3c/browser-payment-api] ShippingAddress versus Address (#189) adamroach
[w3c/browser-payment-api] adding careOf field (#196) adamroach
[w3c/browser-payment-api] Terms and conditions next to "Pay" button (#195) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Use navigator.payments singleton, factory method, or PaymentRequest constructor (#16) Ade Bateman

Friday, 13 May 2016

[w3c/browser-payment-api] Visibility of Payment Options (#194) mattsaxon

Thursday, 12 May 2016

Re: [w3c/browser-payment-api] Explain how to treat unrecognised complete values (#191) Ade Bateman
Re: [w3c/browser-payment-api] Consider revising the design of complete() (#122) Ade Bateman
Re: [w3c/browser-payment-api] Explain how to treat unrecognised complete values (#191) Ade Bateman
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) David I. Lehn
Re: [w3c/browser-payment-api] Update to method identifiers spec to use absolute URLs (#183) Ade Bateman
Re: [w3c/browser-payment-api] Update to method identifiers spec to use absolute URLs (#183) Ade Bateman
Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) Ade Bateman
Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) ianbjacobs
Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) Dave Longley
Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) ianbjacobs
Re: [w3c/browser-payment-api] Should a payment method identifier (URL) resolve to a machine readable resource that describes it? (#46) Dave Longley
Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) Dave Longley
[w3c/browser-payment-api] Rename the address type since it will likely be used for other purposes. (#193) Ade Bateman
Re: [w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192) ianbjacobs
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) adamroach
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Dave Longley
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) ianbjacobs
Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) ianbjacobs
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Dave Longley
Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) Dave Longley
Re: [w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192) Ade Bateman
Re: [w3c/browser-payment-api] Remove delegated state and make abort() return a promise (#190) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Remove delegated state and make abort() return a promise (#190) Ade Bateman
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Reject acceptPromise on abort() (#182) Ade Bateman
Re: [w3c/browser-payment-api] Reject acceptPromise on abort() (#182) Ade Bateman
Re: [w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192) Dave Longley
Re: [w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192) adamroach
Re: [w3c/browser-payment-api] Update to method identifiers spec to use absolute URLs (#183) Dave Longley
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) adamroach
Re: [w3c/browser-payment-api] Remove delegated state and make abort() return a promise (#190) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) adamroach
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Dave Longley
Re: [w3c/browser-payment-api] Update to method identifiers spec to use absolute URLs (#183) Dave Longley
Re: [w3c/browser-payment-api] Time validity of updateWith() (#188) Ade Bateman
Re: [w3c/browser-payment-api] Update promise rejection (#187) adamroach
Re: [w3c/browser-payment-api] Update to method identifiers spec to use absolute URLs (#183) ianbjacobs
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) ianbjacobs
Re: [w3c/browser-payment-api] Time validity of updateWith() (#188) adamroach
Re: [w3c/browser-payment-api] Reject acceptPromise on abort() (#182) adamroach
Re: [w3c/browser-payment-api] ShippingAddress versus Address (#189) Shane McCarron
Re: [w3c/browser-payment-api] Update promise rejection (#187) Ade Bateman
Re: [w3c/browser-payment-api] Update promise rejection (#187) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192) Ade Bateman
Re: [w3c/browser-payment-api] Remove delegated state and make abort() return a promise (#190) Ade Bateman
Re: [w3c/browser-payment-api] Update promise rejection (#187) Ade Bateman
Re: [w3c/browser-payment-api] ShippingAddress versus Address (#189) Ade Bateman
Re: [w3c/browser-payment-api] ShippingAddress versus Address (#189) Tommy Thorsen
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Update promise rejection (#187) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Time validity of updateWith() (#188) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Remove delegated state and make abort() return a promise (#190) Adrian Hope-Bailie
[w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Reject acceptPromise on abort() (#182) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add support for ShippingOption.selected. (#179) Adrian Hope-Bailie

Wednesday, 11 May 2016

Re: [w3c/browser-payment-api] Time validity of updateWith() (#188) Ade Bateman
[w3c/browser-payment-api] Explain how to treat unrecognised complete values (#191) Ade Bateman
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Ade Bateman
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Ade Bateman
[w3c/browser-payment-api] Remove delegated state and make abort() return a promise (#190) Ade Bateman
Re: [w3c/browser-payment-api] Adding support for phone and email (#174) Ade Bateman
Re: [w3c/browser-payment-api] Adding support for phone and email (#174) Ade Bateman
Re: [w3c/browser-payment-api] Should the merchant be able to request your email and recipient phone number (#1) Ade Bateman
Re: [w3c/browser-payment-api] ShippingAddress versus Address (#189) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Adding support for phone and email (#174) mattsaxon
[w3c/browser-payment-api] ShippingAddress versus Address (#189) adamroach
Re: [w3c/browser-payment-api] shippingAddress and "c/o" field (#186) ianbjacobs
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) ianbjacobs

Tuesday, 10 May 2016

[w3c/browser-payment-api] Time validity of updateWith() (#188) adamroach
[w3c/browser-payment-api] Update promise rejection (#187) adamroach
[w3c/browser-payment-api] shippingAddress and "c/o" field (#186) adamroach
[w3c/browser-payment-api] Currency Types and Rendering (#185) adamroach
Re: [w3c/browser-payment-api] Use navigator.payments singleton, factory method, or PaymentRequest constructor (#16) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Use navigator.payments singleton, factory method, or PaymentRequest constructor (#16) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Add support for ShippingOption.selected. (#179) rvm4
Re: [w3c/browser-payment-api] Adding support for phone and email (#174) rvm4
Re: [w3c/browser-payment-api] What semantics is needed for payment method specific data? (#143) ianbjacobs
Re: [w3c/browser-payment-api] What semantics is needed for payment method specific data? (#143) ianbjacobs
Re: [w3c/browser-payment-api] Should the payment mediator pass all payment method data to the payment app or just relevant data? (#157) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] setup CI for automatic publications with echidna (#184) Denis Ah-Kang
Re: [w3c/browser-payment-api] setup CI for automatic publications with echidna (#184) Denis Ah-Kang
Re: [w3c/browser-payment-api] setup CI for automatic publications with echidna (#184) ianbjacobs
Re: [w3c/browser-payment-api] setup CI for automatic publications with echidna (#184) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] API flow (#177) Adrian Hope-Bailie
[w3c/browser-payment-api] setup CI for automatic publications with echidna (#184) Denis Ah-Kang

Monday, 9 May 2016

Re: [w3c/browser-payment-api] API flow (#177) ianbjacobs
Re: [w3c/browser-payment-api] API flow (#177) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] API flow (#177) Adrian Hope-Bailie

Friday, 6 May 2016

Re: [w3c/browser-payment-api] API flow (#177) mattsaxon

Thursday, 5 May 2016

Wednesday, 4 May 2016

Re: [w3c/browser-payment-api] Updated to use [SecureContext] extended attribute. (#172) David I. Lehn
Re: [w3c/browser-payment-api] Updated to use [SecureContext] extended attribute. (#172) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should it be possible to provide amounts in more than one currency (#3) Richard Love
Re: [w3c/browser-payment-api] API flow (#177) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Support for negative amounts (#119) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Support for negative amounts (#119) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Clarified value to use to resove [[acceptPromise]] (#181) Ade Bateman
Re: [w3c/browser-payment-api] Add support for ShippingOption.selected. (#179) adamroach
Re: [w3c/browser-payment-api] Add support for ShippingOption.selected. (#179) Ade Bateman
Re: [w3c/browser-payment-api] Clarified value to use to resove [[acceptPromise]] (#181) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Consider revising the design of complete() (#122) Dave Longley
Re: [w3c/browser-payment-api] Consider revising the design of complete() (#122) adamroach
Re: [w3c/browser-payment-api] Updated to use [SecureContext] extended attribute. (#172) Adrian Hope-Bailie
[w3c/browser-payment-api] Clarified value to use to resove [[acceptPromise]] (#181) adamroach
Re: [w3c/browser-payment-api] Add support for ShippingOption.selected. (#179) adamroach
Re: [w3c/browser-payment-api] Add support for ShippingOption.selected. (#179) Manu Sporny
Re: [w3c/browser-payment-api] Fix two minor typos (#180) Ade Bateman
Re: [w3c/browser-payment-api] Add support for ShippingOption.selected. (#179) Manu Sporny
Re: [w3c/browser-payment-api] Dynamic Currency Conversion (DCC) Support (#178) ianbjacobs
Re: [w3c/browser-payment-api] Add support for ShippingOption.selected. (#179) Manu Sporny
Re: [w3c/browser-payment-api] Fix two minor typos (#180) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add support for ShippingOption.selected. (#179) Manu Sporny
[w3c/browser-payment-api] Fix two minor typos (#180) adamroach
[w3c/browser-payment-api] Add support for ShippingOption.selected. (#179) Ade Bateman
Re: [w3c/browser-payment-api] Fix #129 (#153) mattsaxon
Re: [w3c/browser-payment-api] API flow (#177) mattsaxon
[w3c/browser-payment-api] Dynamic Currency Conversion (DCC) Support (#178) Richard Love
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) kirkalx
Re: [w3c/browser-payment-api] Updated to use [SecureContext] extended attribute. (#172) Manu Sporny
Re: [w3c/browser-payment-api] Adding support for phone and email (#174) Zach Koch

Tuesday, 3 May 2016

Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) Ade Bateman
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) ianbjacobs
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) Shane McCarron
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) Ade Bateman
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) Shane McCarron
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) ianbjacobs
Re: [w3c/browser-payment-api] API flow (#177) ianbjacobs
Re: [w3c/browser-payment-api] API flow (#177) mattsaxon
Re: [w3c/browser-payment-api] Required fields (#176) rvm4
Re: [w3c/browser-payment-api] API flow (#177) Ade Bateman
Re: [w3c/browser-payment-api] Required fields (#176) Ade Bateman
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Remove issue #119 note and assert that total should be non-negative (#168) Ade Bateman
Re: [w3c/browser-payment-api] Remove issue #119 note and assert that total should be non-negative (#168) Ade Bateman
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) Ade Bateman
Re: [w3c/browser-payment-api] Should it be possible to provide amounts in more than one currency (#3) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should PaymentItems have a type? (#163) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Required fields (#176) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should it be possible to provide amounts in more than one currency (#3) rlovetx
Re: [w3c/browser-payment-api] Should PaymentItems have a type? (#163) ianbjacobs
Re: [w3c/browser-payment-api] Should PaymentItems have a type? (#163) Shane McCarron
Re: [w3c/browser-payment-api] Required fields (#176) Shane McCarron
Re: [w3c/browser-payment-api] Fix #129 (#153) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should PaymentItems have a type? (#163) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Required fields (#176) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] API flow (#177) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Required fields (#176) mattsaxon
Re: [w3c/browser-payment-api] Updated examples to reflect changes in recent PRs (acf1150) charlieanna2013
Re: [w3c/browser-payment-api] Fix old reference to items and use total/displayItems (41f8151) charlieanna2013
Re: [w3c/browser-payment-api] Update security and privacy considerations sections (f70fdcd) charlieanna2013
Re: [w3c/browser-payment-api] Update security and privacy considerations sections (f70fdcd) charlieanna2013

Monday, 2 May 2016

Sunday, 1 May 2016

Last message date: Tuesday, 31 May 2016 17:50:11 UTC