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

[w3c/browser-payment-api] Move PMI and Card specs out of repo (#207) Adrian Hope-Bailie (Tuesday, 31 May)

Re: [w3c/browser-payment-api] General Comment on Registry Design (#148) Adrian Hope-Bailie (Tuesday, 31 May)

Re: [w3c/browser-payment-api] Terminology across all Web Payments documents should be aligned (#43) Adrian Hope-Bailie (Tuesday, 31 May)

Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Adrian Hope-Bailie (Tuesday, 31 May)

Re: [w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132) Adrian Hope-Bailie (Tuesday, 31 May)

Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) Adrian Hope-Bailie (Tuesday, 31 May)

Re: [w3c/browser-payment-api] [basic] Reference trademarks (#94) Adrian Hope-Bailie (Tuesday, 31 May)

Re: [w3c/browser-payment-api] Specification to include Flow Diagram (#32) Adrian Hope-Bailie (Tuesday, 31 May)

[w3c/browser-payment-api] Fix bug in updateWith algorithm that resets shippingOption (#206) Ade Bateman (Thursday, 26 May)

Re: [w3c/browser-payment-api] Is it neccessary to distinguish the origin of data provided in the payment response, and how would we do it? (#173) Rouslan Solomakhin (Wednesday, 25 May)

Re: [w3c/browser-payment-api] What happens when currency of offer differs from currency of selected payment instrument? (#29) Rouslan Solomakhin (Wednesday, 25 May)

Re: [w3c/browser-payment-api] Should the API handle pre-auth, recurring payments, and similar scenarios (#19) Adrian Hope-Bailie (Tuesday, 24 May)

[w3c/browser-payment-api] PROPOSAL: Payment Method Identifiers taking advantage of URL characteristics (#205) Adrian Hope-Bailie (Tuesday, 24 May)

[w3c/browser-payment-api] Should the amount be in decimal or cents? (#204) Guille Paz (Sunday, 22 May)

[w3c/browser-payment-api] Why another API? (#203) Thomas Jensen (Saturday, 21 May)

Re: [w3c/browser-payment-api] Specification of required fields (#114) Rouslan Solomakhin (Saturday, 21 May)

[w3c/browser-payment-api] Add missing curly bracket (#202) derekjohnson (Friday, 20 May)

[w3c/browser-payment-api] Removing erroneous <svg> clip boundaries (#201) adamroach (Friday, 20 May)

Re: [w3c/browser-payment-api] Should we define nesting/grouping semantics for payment method identifier matching? (#30) maoyanhua (Thursday, 19 May)

Re: [w3c/browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Jason Normore (Thursday, 19 May)

Re: [w3c/browser-payment-api] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#45) ianbjacobs (Wednesday, 18 May)

Re: [w3c/browser-payment-api] What component does the payment method intersection? (#103) ianbjacobs (Wednesday, 18 May)

Re: [w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) ianbjacobs (Wednesday, 18 May)

Re: [w3c/browser-payment-api] Should well-known identifiers be used for ubiquitous payment methods (#10) Adrian Hope-Bailie (Wednesday, 18 May)

Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) Adrian Hope-Bailie (Wednesday, 18 May)

Re: [w3c/browser-payment-api] Identifiers or Locators (#150) ianbjacobs (Tuesday, 17 May)

Re: [w3c/browser-payment-api] Registry Access/Handling Registry Change (#151) ianbjacobs (Tuesday, 17 May)

[w3c/browser-payment-api] Concern on Payment Method Identifier requirement (#200) maoyanhua (Tuesday, 17 May)

[w3c/browser-payment-api] Storing card information (#199) adamroach (Monday, 16 May)

[w3c/browser-payment-api] Address alignment (#198) adamroach (Monday, 16 May)

[w3c/browser-payment-api] Care of (#197) adamroach (Monday, 16 May)

[w3c/browser-payment-api] adding careOf field (#196) adamroach (Monday, 16 May)

[w3c/browser-payment-api] Terms and conditions next to "Pay" button (#195) Rouslan Solomakhin (Monday, 16 May)

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

Re: [w3c/browser-payment-api] Should a payment method identifier (URL) resolve to a machine readable resource that describes it? (#46) Dave Longley (Thursday, 12 May)

[w3c/browser-payment-api] Rename the address type since it will likely be used for other purposes. (#193) Ade Bateman (Thursday, 12 May)

Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) Dave Longley (Thursday, 12 May)

[w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192) Adrian Hope-Bailie (Thursday, 12 May)

[w3c/browser-payment-api] Explain how to treat unrecognised complete values (#191) Ade Bateman (Wednesday, 11 May)

Re: [w3c/browser-payment-api] Change the way we request user data (#65) Ade Bateman (Wednesday, 11 May)

[w3c/browser-payment-api] Remove delegated state and make abort() return a promise (#190) Ade Bateman (Wednesday, 11 May)

Re: [w3c/browser-payment-api] Should the merchant be able to request your email and recipient phone number (#1) Ade Bateman (Wednesday, 11 May)

[w3c/browser-payment-api] ShippingAddress versus Address (#189) adamroach (Wednesday, 11 May)

[w3c/browser-payment-api] Time validity of updateWith() (#188) adamroach (Tuesday, 10 May)

[w3c/browser-payment-api] Update promise rejection (#187) adamroach (Tuesday, 10 May)

[w3c/browser-payment-api] shippingAddress and "c/o" field (#186) adamroach (Tuesday, 10 May)

[w3c/browser-payment-api] Currency Types and Rendering (#185) adamroach (Tuesday, 10 May)

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 (Tuesday, 10 May)

[w3c/browser-payment-api] setup CI for automatic publications with echidna (#184) Denis Ah-Kang (Tuesday, 10 May)

[w3c/browser-payment-api] Update to method identifiers spec to use absolute URLs (#183) Ade Bateman (Thursday, 5 May)

Re: [w3c/browser-payment-api] Use navigator.payments singleton, factory method, or PaymentRequest constructor (#16) Ade Bateman (Thursday, 5 May)

Re: [w3c/browser-payment-api] BasicCardResponse: cardholderName should be optional. (#134) Ade Bateman (Thursday, 5 May)

Re: [w3c/browser-payment-api] Spec should use [SecureContext] once that is defined in Web IDL (#22) Ade Bateman (Thursday, 5 May)

[w3c/browser-payment-api] Reject acceptPromise on abort() (#182) Ade Bateman (Thursday, 5 May)

Re: [w3c/browser-payment-api] Support for negative amounts (#119) Adrian Hope-Bailie (Wednesday, 4 May)

Re: [w3c/browser-payment-api] Consider revising the design of complete() (#122) adamroach (Wednesday, 4 May)

[w3c/browser-payment-api] Clarified value to use to resove [[acceptPromise]] (#181) adamroach (Wednesday, 4 May)

[w3c/browser-payment-api] Fix two minor typos (#180) adamroach (Wednesday, 4 May)

[w3c/browser-payment-api] Add support for ShippingOption.selected. (#179) Ade Bateman (Wednesday, 4 May)

[w3c/browser-payment-api] Dynamic Currency Conversion (DCC) Support (#178) Richard Love (Wednesday, 4 May)

Re: [w3c/browser-payment-api] Remove issue #119 note and assert that total should be non-negative (#168) Ade Bateman (Tuesday, 3 May)

Re: [w3c/browser-payment-api] Should it be possible to provide amounts in more than one currency (#3) rlovetx (Tuesday, 3 May)

Re: [w3c/browser-payment-api] API flow (#177) Adrian Hope-Bailie (Tuesday, 3 May)

Re: [w3c/browser-payment-api] Updated examples to reflect changes in recent PRs (acf1150) charlieanna2013 (Tuesday, 3 May)

Re: [w3c/browser-payment-api] Fix old reference to items and use total/displayItems (41f8151) charlieanna2013 (Tuesday, 3 May)

Re: [w3c/browser-payment-api] Update security and privacy considerations sections (f70fdcd) charlieanna2013 (Tuesday, 3 May)

Re: [w3c/browser-payment-api] Adding support for phone and email (#174) ianbjacobs (Monday, 2 May)

Re: [w3c/browser-payment-api] Updated to use [SecureContext] extended attribute. (#172) Zach Koch (Monday, 2 May)

Re: [w3c/browser-payment-api] Required fields (#176) Zach Koch (Monday, 2 May)

Re: [w3c/browser-payment-api] What semantics is needed for payment method specific data? (#143) ianbjacobs (Monday, 2 May)

Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) kirkalx (Sunday, 1 May)

Re: [w3c/browser-payment-api] Should PaymentItems have a type? (#163) Nick Shearer (Sunday, 1 May)

Re: [w3c/browser-payment-api] Fix #129 (#153) Nick S (Sunday, 1 May)

Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) Manu Sporny (Sunday, 1 May)

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