public-webpayments-specs@w3.org from February 2017 by date

Tuesday, 28 February 2017

• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) Adrian Hope-Bailie
• [w3c/browser-payment-api] Addition of flag on PaymentMethodData to indicate that line items should be shared with apps (#446) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) Adrian Hope-Bailie
• [w3c/browser-payment-api] Create pr-preview config file. (#445) Tobie Langel
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) ianbjacobs
• Re: [w3c/browser-payment-api] Fix markup errors that broke autopublishing (#444) ianbjacobs
• Re: [w3c/browser-payment-api] Fix markup errors that broke autopublishing (#444) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) Tommy Thorsen
• [w3c/browser-payment-api] Fix markup errors that broke autopublishing (#444) Michael[tm] Smith
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) Tommy Thorsen
• Re: [w3c/browser-payment-api] Making this API work with HTML Forms (#330) Marcos Cáceres
• Re: [w3c/browser-payment-api] Making this API work with HTML Forms (#330) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: s/fields/members + xref fixes (closes #424) (#443) Marcos Cáceres
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Marcos Cáceres
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Marcos Cáceres
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Marcos Cáceres
• [w3c/browser-payment-api] editorial: s/fields/members + xref fixes (closes #424) (#443) Marcos Cáceres
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) Marcos Cáceres

Monday, 27 February 2017

• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) Addison Phillips
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) Marcos Cáceres
• [w3c/browser-payment-api] PaymentResponse attributes should be separate sections (#442) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: firing event not done correctly (closes #401) (#433) Marcos Cáceres
• Re: [w3c/browser-payment-api] firing an event is not done correctly (#401) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: firing event not done correctly (closes #401) (#433) Marcos Cáceres

Friday, 24 February 2017

• Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) Anders Rundgren
• Re: [w3c/browser-payment-api] `country` vs `sortingCode` (#434) Eiji Kitamura
• Re: [w3c/browser-payment-api] `country` vs `sortingCode` (#434) Eiji Kitamura

Thursday, 23 February 2017

• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) Domenic Denicola

Friday, 24 February 2017

• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Marcos Cáceres
• Re: [w3c/browser-payment-api] Is 'currencySystem' required? (#408) Marcos Cáceres
• Re: [w3c/browser-payment-api] fix: IDL dictates what is/isn't required (closes #408) (#431) Marcos Cáceres
• Re: [w3c/browser-payment-api] fix: IDL dictates what is/isn't required (closes #408) (#431) Marcos Cáceres

Thursday, 23 February 2017

• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) Domenic Denicola
• Re: [w3c/browser-payment-api] Define payment option filtering algorithm. (#420) ianbjacobs
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) Domenic Denicola
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Domenic Denicola
• Re: [w3c/browser-payment-api] Editorial: firing event not done correctly (closes #401) (#433) Domenic Denicola
• Re: [w3c/browser-payment-api] fix: IDL dictates what is/isn't required (closes #408) (#431) Domenic Denicola
• Re: [w3c/browser-payment-api] Drop redundant reference to secure context + other redefinitions (#399) Domenic Denicola
• Re: [w3c/browser-payment-api] editorial: don't redefine WebIDL things (closes #399) (#430) Domenic Denicola
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Domenic Denicola
• Re: [w3c/browser-payment-api] Collect Privacy and Security considerations (#331) Marcos Cáceres
• Re: [w3c/webpayments-method-identifiers] Support for PMI's with schemes other than https? (#17) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] Support for PMI's with schemes other than https? (#17) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] `country` vs `sortingCode` (#434) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Marcos Cáceres
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Editorial: define and link to the different states (#376) Marcos Cáceres
• Re: [w3c/browser-payment-api] fix: IDL dictates what is/isn't required (closes #408) (#431) Marcos Cáceres
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Ben Tian
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Ben Tian
• [w3c/browser-payment-api] editorial: s/shown/presented (closes #428) (#435) Marcos Cáceres
• [w3c/browser-payment-api] markup issues (#441) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) Marcos Cáceres
• [w3c/browser-payment-api] Authors are not conformance classes (#440) Marcos Cáceres
• [w3c/browser-payment-api] RCF2119 keywords in informative sections (#439) Marcos Cáceres
• Re: [w3c/browser-payment-api] Collect Privacy and Security considerations (#331) Marcos Cáceres
• [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) Marcos Cáceres
• [w3c/browser-payment-api] Web page and developer (#437) Marcos Cáceres
• [w3c/browser-payment-api] Initial values for internal slots (#436) Marcos Cáceres
• Re: [w3c/browser-payment-api] What is the mechanism for limiting repeated calls to canMakePayments ? (#367) Marcos Cáceres
• [w3c/browser-payment-api] `country` vs `sortingCode` (#434) Eiji Kitamura
• Re: [w3c/browser-payment-api] PaymentRequest does not handle the case of store pickup (#389) Marcos Cáceres
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] `country` vs `sortingCode` (#434) Marcos Cáceres
• Re: [w3c/browser-payment-api] What is the mechanism for limiting repeated calls to canMakePayments ? (#367) ianbjacobs
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] How are currency systems expected to be implemented in practice? (#343) Marcos Cáceres
• [w3c/browser-payment-api] Editorial: firing event not done correctly (closes #401) (#433) Marcos Cáceres
• Re: [w3c/browser-payment-api] put request id in details dictionary (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] PaymentApp fails to abort payment flow (#384) Marcos Cáceres
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] What is the mechanism for limiting repeated calls to canMakePayments ? (#367) Marcos Cáceres
• Re: [w3c/browser-payment-api] How are currency systems expected to be implemented in practice? (#343) Marcos Cáceres
• Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) Marcos Cáceres
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) Marcos Cáceres
• Re: [w3c/browser-payment-api] Throwing exceptions rather than permitting broken usage (#275) Marcos Cáceres
• Re: [w3c/browser-payment-api] Throwing exceptions rather than permitting broken usage (#275) Marcos Cáceres
• [w3c/browser-payment-api] fix: s/user interaction/transaction (closes #402) (#432) Marcos Cáceres
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Marcos Cáceres
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Domenic Denicola
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (closes #388, #412) (#426) Domenic Denicola
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) Marcos Cáceres
• [w3c/browser-payment-api] editorial: don't redefine WebIDL things (closes #399) (#430) Marcos Cáceres
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (closes #388, #412) (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (closes #388, #412) (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] fix: IDL dictates what is/isn't required (closes #408) (#431) ianbjacobs
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (closes #388, #412) (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] fix: IDL dictates what is/isn't required (closes #408) (#431) Marcos Cáceres
• [w3c/browser-payment-api] fix: IDL dictates what is/isn't required (closes #408) (#431) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: dfn payment request states as strings (closes #376) (#429) Marcos Cáceres
• Re: [w3c/browser-payment-api] put request id in details dictionary (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] put request id in details dictionary (#426) Domenic Denicola
• Re: [w3c/browser-payment-api] editorial: dfn payment request states as strings (closes #376) (#429) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: dfn payment request states as strings (closes #376) (#429) Domenic Denicola
• [w3c/browser-payment-api] editorial: dfn payment request states as strings (closes #376) (#429) Marcos Cáceres
• [w3c/browser-payment-api] "Shown" should be "presented" in prose (#428) Marcos Cáceres
• Re: [w3c/browser-payment-api] put request id in details dictionary (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] put request id in details dictionary (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] put request id in details dictionary (#426) Marcos Cáceres
• Re: [w3c/browser-payment-api] put request id in details dictionary (#426) Marcos Cáceres

Wednesday, 22 February 2017

• Re: [w3c/browser-payment-api] Group payment dictionaries into a section (#427) Marcos Cáceres
• [w3c/browser-payment-api] Group payment dictionaries into a section (#427) Marcos Cáceres
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) Tommy Thorsen
• Re: [w3c/browser-payment-api] put request id in details dictionary (#426) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) rvm4
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) rvm4
• [w3c/browser-payment-api] put request id in details dictionary (#426) rvm4
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) adamroach
• [w3c/webpayments-methods-card] Add link to list of card networks (#25) ianbjacobs
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) Domenic Denicola
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Domenic Denicola
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) Salvador de la Puente González
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) Tommy Thorsen
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: fix linking to various specs (#423) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: Add missing xrefs to various specs (#400) Marcos Cáceres
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) Molly Dalton
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) Nick Schonning
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) rvm4
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Marcos Cáceres
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) Marcos Cáceres

Tuesday, 21 February 2017

• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) rvm4
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) Tommy Thorsen
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) Domenic Denicola
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Domenic Denicola
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) adamroach
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) adamroach
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) Tommy Thorsen
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) Domenic Denicola
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) ianbjacobs
• [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) Tommy Thorsen
• Re: [w3c/browser-payment-api] Editorial: don't capitalize RFC 2119 terms (#377) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial: don't capitalize RFC 2119 terms (#377) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) Ben Tian
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) Ben Tian
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) Marcos Cáceres

Monday, 20 February 2017

• [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) adamroach
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) ianbjacobs
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) Dave Longley
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) Domenic Denicola
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) Marcos Cáceres
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) Manu Sporny
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) Simon Pieters
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) Tommy Thorsen
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) Marcos Cáceres
• Re: [w3c/browser-payment-api] Throwing exceptions rather than permitting broken usage (#275) Marcos Cáceres
• Re: [w3c/browser-payment-api] DOMStrings don't contain "characters" (#322) Marcos Cáceres
• [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) Marcos Cáceres
• [w3c/browser-payment-api] Spec talks about dictionary fields instead of dictionary members (#424) Marcos Cáceres
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) Marcos Cáceres
• Re: [w3c/browser-payment-api] Dynamic Currency Conversion requirements (#289) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial fixes and xrefs (#422) Marcos Cáceres
• Re: [w3c/browser-payment-api] Editorial fixes and xrefs (#422) Marcos Cáceres
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) Marcos Cáceres
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: fix linking to various specs (#423) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: fix linking to various specs (#423) Marcos Cáceres

Saturday, 18 February 2017

• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) Molly Dalton

Friday, 17 February 2017

• Re: [w3c/browser-payment-api] editorial: fix linking to various specs (#423) Domenic Denicola
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) Zach Koch
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Jake Archibald
• Re: [w3c/browser-payment-api] editorial: s/character/code unit/ (closes #322) (#421) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Dave Longley
• Re: [w3c/browser-payment-api] editorial: s/character/code unit/ (closes #322) (#421) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: s/character/code unit/ (closes #322) (#421) Domenic Denicola
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Tommy Thorsen
• Re: [w3c/browser-payment-api] editorial: s/character/code unit/ (closes #322) (#421) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: s/character/code unit/ (closes #322) (#421) Simon Pieters
• Re: [w3c/browser-payment-api] editorial: fix linking to DOM spec (#423) Marcos Cáceres
• [w3c/webpayments-method-identifiers] Payment Method Identifier needs dfn (#23) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: fix linking to DOM spec (#423) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: fix linking to DOM spec (#423) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: s/character/code unit/ (closes #322) (#421) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: s/character/code point/ (closes #322) (#421) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Dave Longley
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) adamroach

Thursday, 16 February 2017

• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Tommy Thorsen
• Re: [w3c/browser-payment-api] editorial: s/character/code point/ (closes #322) (#421) Simon Pieters
• [w3c/browser-payment-api] editorial: fix linking to DOM spec (#423) Marcos Cáceres
• [w3c/browser-payment-api] Editorial fixes and xrefs (#422) Marcos Cáceres
• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) Marcos Cáceres
• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) Marcos Cáceres
• [w3c/browser-payment-api] editorial: s/character/code point/ (closes #322) (#421) Marcos Cáceres
• Re: [w3c/browser-payment-api] Response/Request semantics and cancellation (#298) Marcos Cáceres
• Re: [w3c/browser-payment-api] Response/Request semantics and cancellation (#298) Marcos Cáceres

Wednesday, 15 February 2017

• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) Marcos Cáceres
• Re: [w3c/browser-payment-api] What is the shippingAddress/shippingOption of a PaymentResponse if requestShipping was false? (#352) Marcos Cáceres
• Re: [w3c/browser-payment-api] Set all the attributes of PaymentResponse when creating it (#417) Marcos Cáceres
• Re: [w3c/browser-payment-api] Set all the attributes of PaymentResponse when creating it (#417) Marcos Cáceres
• Re: [w3c/browser-payment-api] paymentRequestID is spelled wrong :( (#414) Marcos Cáceres
• Re: [w3c/browser-payment-api] BREAKING CHANGE: s/paymentRequestID/paymentRequestId (closes #414) (#419) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) Manu Sporny
• Re: [w3c/webpayments-payment-apps-api] Don't send display items to payment handler (#103) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Don't send display items to payment handler (#103) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• [w3c/webpayments-payment-apps-api] Don't send display items to payment handler (#103) Marcos Cáceres

Tuesday, 14 February 2017

• Re: [w3c/browser-payment-api] Define payment option filtering algorithm. (#420) Domenic Denicola
• Re: [w3c/browser-payment-api] Define payment option filtering algorithm. (#420) adamroach
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Define payment option filtering algorithm. (#420) Rouslan Solomakhin
• [w3c/browser-payment-api] Define payment option filtering algorithm. (#420) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Simplify Example 3 as per issue #82 (#101) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Clarification on Payment App "Options" (#90) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Clarification on Payment App "Options" (#90) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) ianbjacobs

Monday, 13 February 2017

• Re: [w3c/browser-payment-api] BREAKING CHANGE: s/paymentRequestID/paymentRequestId (closes #414) (#419) Domenic Denicola
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) Simon Pieters
• Re: [w3c/browser-payment-api] BREAKING CHANGE: s/paymentRequestID/paymentRequestId (closes #414) (#419) Simon Pieters
• Re: [w3c/webpayments-method-identifiers] Circular dependency between PMI and PR specs (#22) Marcos Cáceres
• Re: [w3c/webpayments-method-identifiers] SRI on manifest (#18) Marcos Cáceres
• [w3c/browser-payment-api] BREAKING CHANGE: s/paymentRequestID/paymentRequestId (closes #414) (#419) Marcos Cáceres
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Recommended payment apps (#74) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Recommended payment apps (#74) Marcos Cáceres

Friday, 10 February 2017

• Re: [w3c/webpayments-payment-apps-api] Recommended payment apps (#74) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) ianbjacobs
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) Marcos Cáceres
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) Marcos Cáceres
• Re: [w3c/browser-payment-api] Update the shippingType option to not allow invalid strings (#416) Marcos Cáceres
• Re: [w3c/browser-payment-api] Why is the "shippingType" member of PaymentOptions not a PaymentShippingType? (#337) Marcos Cáceres
• Re: [w3c/browser-payment-api] Update the shippingType option to not allow invalid strings (#416) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Marcos Cáceres
• Re: [w3c/browser-payment-api] paymentRequestID is spelled wrong :( (#414) Marcos Cáceres
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) Marcos Cáceres

Thursday, 9 February 2017

• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) Zach Koch
• [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) Domenic Denicola
• [w3c/browser-payment-api] Set all the attributes of PaymentResponse when creating it (#417) Domenic Denicola
• [w3c/browser-payment-api] Update the shippingType option to not allow invalid strings (#416) Domenic Denicola
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) Domenic Denicola
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) rvm4
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) rvm4
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) ianbjacobs
• Re: [w3c/browser-payment-api] Why is the "shippingType" member of PaymentOptions not a PaymentShippingType? (#337) Zach Koch
• Re: [w3c/webpayments-payment-apps-api] Clarification on Payment App "Options" (#90) ianbjacobs
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) ianbjacobs
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) Marcos Cáceres
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) Marcos Cáceres
• Re: [w3c/browser-payment-api] paymentRequestID is spelled wrong :( (#414) Marcos Cáceres
• Re: [w3c/browser-payment-api] paymentRequestID is spelled wrong :( (#414) Marcos Cáceres
• Re: [w3c/browser-payment-api] paymentRequestID is spelled wrong :( (#414) Marcos Cáceres
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) Zach Koch
• Re: [w3c/browser-payment-api] paymentRequestID is spelled wrong :( (#414) Marcos Cáceres

Wednesday, 8 February 2017

• [w3c/browser-payment-api] It is never stated how the payment request ID is used (#415) Domenic Denicola
• [w3c/browser-payment-api] paymentRequestID is spelled wrong :( (#414) Domenic Denicola
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) Domenic Denicola
• Re: [w3c/browser-payment-api] updateWith will silently ignore data in hard-to-debug ways (#350) Domenic Denicola
• Re: [w3c/browser-payment-api] updateWith will silently ignore data in hard-to-debug ways (#350) Marcos Cáceres
• Re: [w3c/browser-payment-api] Introduction is aspirational, but misleading (#410) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial(intro): drop hyperbolic statements (closes #410) (#411) Marcos Cáceres
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Recommended payment apps (#74) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) Marcos Cáceres
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) rvm4
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) rvm4

Tuesday, 7 February 2017

• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Tommy Thorsen
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) Domenic Denicola
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) rvm4
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) rvm4
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) rvm4
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) rvm4
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) Rouslan Solomakhin
• [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) rvm4
• Re: [w3c/browser-payment-api] PaymentRequestID initialization (#412) rvm4
• Re: [w3c/browser-payment-api] PaymentRequestID initialization (#412) Rouslan Solomakhin
• [w3c/browser-payment-api] PaymentRequestID initialization (#412) rvm4
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Recovery of a failed Push Payment (#102) Conor Hackett
• Re: [w3c/webpayments-payment-apps-api] Recovery of a failed Push Payment (#102) Conor Hackett
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Nick Shearer
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Marcos Cáceres

Monday, 6 February 2017

• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) Tommy Thorsen
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) Adrian Hope-Bailie
• [w3c/browser-payment-api] editorial(intro): drop hyperbolic statements (closes #410) (#411) Marcos Cáceres
• Re: [w3c/browser-payment-api] Introduction is aspirational, but misleading (#410) Marcos Cáceres
• [w3c/browser-payment-api] Introduction is aspirational, but misleading (#410) Marcos Cáceres

Friday, 3 February 2017

• Re: [w3c/webpayments-payment-apps-api] Recovery of a failed Push Payment (#102) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) ianbjacobs
• [w3c/webpayments-payment-apps-api] Recovery of a failed Push Payment (#102) Conor Hackett
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) Tommy Thorsen
• [w3c/webpayments-payment-apps-api] Simplify Example 3 as per issue #82 (#101) Tommy Thorsen
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) Adrian Hope-Bailie
• [w3c/webpayments-method-identifiers] Circular dependency between PMI and PR specs (#22) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] SRI on manifest (#18) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] update pmi spec with apen and proprietary payment method identifiers (#10) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] update pmi spec with apen and proprietary payment method identifiers (#10) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] slight rewording (#6) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] slight rewording (#6) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] update pmi spec with apen and proprietary payment method identifiers (#10) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Tommy Thorsen

Thursday, 2 February 2017

• Re: [w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) adamroach
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) adamroach

Wednesday, 1 February 2017

• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) Rouslan Solomakhin

Last message date: Tuesday, 28 February 2017 19:49:15 UTC