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

adamroach

• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) (Wednesday, 22 February)
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) (Tuesday, 21 February)
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) (Tuesday, 21 February)
• [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) (Monday, 20 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 17 February)
• Re: [w3c/browser-payment-api] Define payment option filtering algorithm. (#420) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Thursday, 2 February)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Thursday, 2 February)

Addison Phillips

• Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) (Monday, 27 February)

Adrian Hope-Bailie

• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Tuesday, 28 February)
• [w3c/browser-payment-api] Addition of flag on PaymentMethodData to indicate that line items should be shared with apps (#446) (Tuesday, 28 February)
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Tuesday, 28 February)
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Tuesday, 28 February)
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Tuesday, 28 February)
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Tuesday, 28 February)
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Monday, 27 February)
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) (Thursday, 23 February)
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) (Thursday, 23 February)
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) (Thursday, 23 February)
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) (Monday, 20 February)
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) (Monday, 20 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Thursday, 16 February)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Thursday, 9 February)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Thursday, 9 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 8 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 8 February)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Wednesday, 8 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 7 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 7 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 7 February)
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) (Monday, 6 February)
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) (Monday, 6 February)
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) (Monday, 6 February)
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) (Friday, 3 February)
• [w3c/webpayments-method-identifiers] Circular dependency between PMI and PR specs (#22) (Friday, 3 February)
• Re: [w3c/webpayments-method-identifiers] SRI on manifest (#18) (Friday, 3 February)
• Re: [w3c/webpayments-method-identifiers] update pmi spec with apen and proprietary payment method identifiers (#10) (Friday, 3 February)
• Re: [w3c/webpayments-method-identifiers] update pmi spec with apen and proprietary payment method identifiers (#10) (Friday, 3 February)
• Re: [w3c/webpayments-method-identifiers] slight rewording (#6) (Friday, 3 February)
• Re: [w3c/webpayments-method-identifiers] slight rewording (#6) (Friday, 3 February)
• Re: [w3c/webpayments-method-identifiers] update pmi spec with apen and proprietary payment method identifiers (#10) (Friday, 3 February)

Anders Rundgren

• Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) (Friday, 24 February)

Ben Tian

• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Thursday, 23 February)
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) (Tuesday, 21 February)
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) (Tuesday, 21 February)

Conor Hackett

• Re: [w3c/webpayments-payment-apps-api] Recovery of a failed Push Payment (#102) (Tuesday, 7 February)
• Re: [w3c/webpayments-payment-apps-api] Recovery of a failed Push Payment (#102) (Tuesday, 7 February)
• [w3c/webpayments-payment-apps-api] Recovery of a failed Push Payment (#102) (Friday, 3 February)

Dave Longley

• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Tuesday, 28 February)
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) (Monday, 20 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 17 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 17 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 17 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 17 February)

Domenic Denicola

• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] Editorial: firing event not done correctly (closes #401) (#433) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] fix: IDL dictates what is/isn't required (closes #408) (#431) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] Drop redundant reference to secure context + other redefinitions (#399) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] editorial: don't redefine WebIDL things (closes #399) (#430) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (closes #388, #412) (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] editorial: dfn payment request states as strings (closes #376) (#429) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Wednesday, 22 February)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Wednesday, 22 February)
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Tuesday, 21 February)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Tuesday, 21 February)
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Tuesday, 21 February)
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Monday, 20 February)
• Re: [w3c/browser-payment-api] editorial: fix linking to various specs (#423) (Friday, 17 February)
• Re: [w3c/browser-payment-api] editorial: s/character/code unit/ (closes #322) (#421) (Friday, 17 February)
• Re: [w3c/browser-payment-api] Define payment option filtering algorithm. (#420) (Tuesday, 14 February)
• Re: [w3c/browser-payment-api] BREAKING CHANGE: s/paymentRequestID/paymentRequestId (closes #414) (#419) (Monday, 13 February)
• [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Thursday, 9 February)
• [w3c/browser-payment-api] Set all the attributes of PaymentResponse when creating it (#417) (Thursday, 9 February)
• [w3c/browser-payment-api] Update the shippingType option to not allow invalid strings (#416) (Thursday, 9 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Thursday, 9 February)
• [w3c/browser-payment-api] It is never stated how the payment request ID is used (#415) (Wednesday, 8 February)
• [w3c/browser-payment-api] paymentRequestID is spelled wrong :( (#414) (Wednesday, 8 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Wednesday, 8 February)
• Re: [w3c/browser-payment-api] updateWith will silently ignore data in hard-to-debug ways (#350) (Wednesday, 8 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Tuesday, 7 February)

Eiji Kitamura

• Re: [w3c/browser-payment-api] `country` vs `sortingCode` (#434) (Friday, 24 February)
• Re: [w3c/browser-payment-api] `country` vs `sortingCode` (#434) (Friday, 24 February)
• [w3c/browser-payment-api] `country` vs `sortingCode` (#434) (Thursday, 23 February)

ianbjacobs

• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Tuesday, 28 February)
• Re: [w3c/browser-payment-api] Fix markup errors that broke autopublishing (#444) (Tuesday, 28 February)
• Re: [w3c/browser-payment-api] Define payment option filtering algorithm. (#420) (Thursday, 23 February)
• Re: [w3c/webpayments-method-identifiers] Support for PMI's with schemes other than https? (#17) (Thursday, 23 February)
• Re: [w3c/webpayments-method-identifiers] Support for PMI's with schemes other than https? (#17) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] What is the mechanism for limiting repeated calls to canMakePayments ? (#367) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] fix: IDL dictates what is/isn't required (closes #408) (#431) (Thursday, 23 February)
• [w3c/webpayments-methods-card] Add link to list of card networks (#25) (Wednesday, 22 February)
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Tuesday, 21 February)
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) (Tuesday, 21 February)
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Tuesday, 21 February)
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) (Monday, 20 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Thursday, 16 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Thursday, 16 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 15 February)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Wednesday, 15 February)
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] Simplify Example 3 as per issue #82 (#101) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] Clarification on Payment App "Options" (#90) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] Clarification on Payment App "Options" (#90) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 14 February)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Friday, 10 February)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Thursday, 9 February)
• Re: [w3c/webpayments-payment-apps-api] Clarification on Payment App "Options" (#90) (Thursday, 9 February)
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Thursday, 9 February)
• Re: [w3c/webpayments-payment-apps-api] Recommended payment apps (#74) (Wednesday, 8 February)
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) (Wednesday, 8 February)
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) (Tuesday, 7 February)
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) (Monday, 6 February)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 3 February)
• Re: [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) (Friday, 3 February)
• Re: [w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19) (Thursday, 2 February)
• Re: [w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19) (Thursday, 2 February)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Wednesday, 1 February)

Jake Archibald

• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 17 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 17 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 17 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Thursday, 16 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Thursday, 16 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Thursday, 16 February)

Manu Sporny

• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) (Monday, 20 February)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Wednesday, 15 February)

Marcos Cáceres

• Re: [w3c/browser-payment-api] Fix markup errors that broke autopublishing (#444) (Tuesday, 28 February)
• Re: [w3c/browser-payment-api] Making this API work with HTML Forms (#330) (Tuesday, 28 February)
• Re: [w3c/browser-payment-api] Making this API work with HTML Forms (#330) (Tuesday, 28 February)
• Re: [w3c/browser-payment-api] editorial: s/fields/members + xref fixes (closes #424) (#443) (Tuesday, 28 February)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Tuesday, 28 February)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Tuesday, 28 February)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Tuesday, 28 February)
• [w3c/browser-payment-api] editorial: s/fields/members + xref fixes (closes #424) (#443) (Tuesday, 28 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Tuesday, 28 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Tuesday, 28 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Monday, 27 February)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Monday, 27 February)
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Monday, 27 February)
• [w3c/browser-payment-api] PaymentResponse attributes should be separate sections (#442) (Monday, 27 February)
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Monday, 27 February)
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Monday, 27 February)
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Monday, 27 February)
• Re: [w3c/browser-payment-api] Editorial: firing event not done correctly (closes #401) (#433) (Monday, 27 February)
• Re: [w3c/browser-payment-api] firing an event is not done correctly (#401) (Monday, 27 February)
• Re: [w3c/browser-payment-api] Editorial: firing event not done correctly (closes #401) (#433) (Monday, 27 February)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Friday, 24 February)
• Re: [w3c/browser-payment-api] Is 'currencySystem' required? (#408) (Friday, 24 February)
• Re: [w3c/browser-payment-api] fix: IDL dictates what is/isn't required (closes #408) (#431) (Friday, 24 February)
• Re: [w3c/browser-payment-api] fix: IDL dictates what is/isn't required (closes #408) (#431) (Friday, 24 February)
• Re: [w3c/browser-payment-api] Collect Privacy and Security considerations (#331) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] Editorial: define and link to the different states (#376) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] fix: IDL dictates what is/isn't required (closes #408) (#431) (Thursday, 23 February)
• [w3c/browser-payment-api] editorial: s/shown/presented (closes #428) (#435) (Thursday, 23 February)
• [w3c/browser-payment-api] markup issues (#441) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Thursday, 23 February)
• [w3c/browser-payment-api] Authors are not conformance classes (#440) (Thursday, 23 February)
• [w3c/browser-payment-api] RCF2119 keywords in informative sections (#439) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] Collect Privacy and Security considerations (#331) (Thursday, 23 February)
• [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Thursday, 23 February)
• [w3c/browser-payment-api] Web page and developer (#437) (Thursday, 23 February)
• [w3c/browser-payment-api] Initial values for internal slots (#436) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] What is the mechanism for limiting repeated calls to canMakePayments ? (#367) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] PaymentRequest does not handle the case of store pickup (#389) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] `country` vs `sortingCode` (#434) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] How are currency systems expected to be implemented in practice? (#343) (Thursday, 23 February)
• [w3c/browser-payment-api] Editorial: firing event not done correctly (closes #401) (#433) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] PaymentApp fails to abort payment flow (#384) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] What is the mechanism for limiting repeated calls to canMakePayments ? (#367) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] How are currency systems expected to be implemented in practice? (#343) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] Throwing exceptions rather than permitting broken usage (#275) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] Throwing exceptions rather than permitting broken usage (#275) (Thursday, 23 February)
• [w3c/browser-payment-api] fix: s/user interaction/transaction (closes #402) (#432) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Thursday, 23 February)
• [w3c/browser-payment-api] editorial: don't redefine WebIDL things (closes #399) (#430) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (closes #388, #412) (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (closes #388, #412) (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (closes #388, #412) (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] fix: IDL dictates what is/isn't required (closes #408) (#431) (Thursday, 23 February)
• [w3c/browser-payment-api] fix: IDL dictates what is/isn't required (closes #408) (#431) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] editorial: dfn payment request states as strings (closes #376) (#429) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] editorial: dfn payment request states as strings (closes #376) (#429) (Thursday, 23 February)
• [w3c/browser-payment-api] editorial: dfn payment request states as strings (closes #376) (#429) (Thursday, 23 February)
• [w3c/browser-payment-api] "Shown" should be "presented" in prose (#428) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] Group payment dictionaries into a section (#427) (Wednesday, 22 February)
• [w3c/browser-payment-api] Group payment dictionaries into a section (#427) (Wednesday, 22 February)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Wednesday, 22 February)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Wednesday, 22 February)
• Re: [w3c/browser-payment-api] editorial: fix linking to various specs (#423) (Wednesday, 22 February)
• Re: [w3c/browser-payment-api] Editorial: Add missing xrefs to various specs (#400) (Wednesday, 22 February)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Wednesday, 22 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Wednesday, 22 February)
• Re: [w3c/browser-payment-api] Editorial: don't capitalize RFC 2119 terms (#377) (Tuesday, 21 February)
• Re: [w3c/browser-payment-api] Editorial: don't capitalize RFC 2119 terms (#377) (Tuesday, 21 February)
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) (Tuesday, 21 February)
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) (Monday, 20 February)
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Monday, 20 February)
• Re: [w3c/browser-payment-api] Throwing exceptions rather than permitting broken usage (#275) (Monday, 20 February)
• Re: [w3c/browser-payment-api] DOMStrings don't contain "characters" (#322) (Monday, 20 February)
• [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Monday, 20 February)
• [w3c/browser-payment-api] Spec talks about dictionary fields instead of dictionary members (#424) (Monday, 20 February)
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) (Monday, 20 February)
• Re: [w3c/browser-payment-api] Dynamic Currency Conversion requirements (#289) (Monday, 20 February)
• Re: [w3c/browser-payment-api] Editorial fixes and xrefs (#422) (Monday, 20 February)
• Re: [w3c/browser-payment-api] Editorial fixes and xrefs (#422) (Monday, 20 February)
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) (Monday, 20 February)
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) (Monday, 20 February)
• Re: [w3c/browser-payment-api] editorial: fix linking to various specs (#423) (Monday, 20 February)
• Re: [w3c/browser-payment-api] editorial: fix linking to various specs (#423) (Monday, 20 February)
• Re: [w3c/browser-payment-api] editorial: s/character/code unit/ (closes #322) (#421) (Friday, 17 February)
• Re: [w3c/browser-payment-api] editorial: s/character/code unit/ (closes #322) (#421) (Friday, 17 February)
• Re: [w3c/browser-payment-api] editorial: s/character/code unit/ (closes #322) (#421) (Friday, 17 February)
• Re: [w3c/browser-payment-api] editorial: fix linking to DOM spec (#423) (Friday, 17 February)
• [w3c/webpayments-method-identifiers] Payment Method Identifier needs dfn (#23) (Friday, 17 February)
• Re: [w3c/browser-payment-api] editorial: fix linking to DOM spec (#423) (Friday, 17 February)
• Re: [w3c/browser-payment-api] editorial: fix linking to DOM spec (#423) (Friday, 17 February)
• Re: [w3c/browser-payment-api] editorial: s/character/code unit/ (closes #322) (#421) (Friday, 17 February)
• Re: [w3c/browser-payment-api] editorial: s/character/code point/ (closes #322) (#421) (Friday, 17 February)
• [w3c/browser-payment-api] editorial: fix linking to DOM spec (#423) (Thursday, 16 February)
• [w3c/browser-payment-api] Editorial fixes and xrefs (#422) (Thursday, 16 February)
• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) (Thursday, 16 February)
• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) (Thursday, 16 February)
• [w3c/browser-payment-api] editorial: s/character/code point/ (closes #322) (#421) (Thursday, 16 February)
• Re: [w3c/browser-payment-api] Response/Request semantics and cancellation (#298) (Thursday, 16 February)
• Re: [w3c/browser-payment-api] Response/Request semantics and cancellation (#298) (Thursday, 16 February)
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Wednesday, 15 February)
• Re: [w3c/browser-payment-api] What is the shippingAddress/shippingOption of a PaymentResponse if requestShipping was false? (#352) (Wednesday, 15 February)
• Re: [w3c/browser-payment-api] Set all the attributes of PaymentResponse when creating it (#417) (Wednesday, 15 February)
• Re: [w3c/browser-payment-api] Set all the attributes of PaymentResponse when creating it (#417) (Wednesday, 15 February)
• Re: [w3c/browser-payment-api] paymentRequestID is spelled wrong :( (#414) (Wednesday, 15 February)
• Re: [w3c/browser-payment-api] BREAKING CHANGE: s/paymentRequestID/paymentRequestId (closes #414) (#419) (Wednesday, 15 February)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Wednesday, 15 February)
• Re: [w3c/webpayments-payment-apps-api] Don't send display items to payment handler (#103) (Wednesday, 15 February)
• Re: [w3c/webpayments-payment-apps-api] Don't send display items to payment handler (#103) (Wednesday, 15 February)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Wednesday, 15 February)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Wednesday, 15 February)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Wednesday, 15 February)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Wednesday, 15 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 15 February)
• [w3c/webpayments-payment-apps-api] Don't send display items to payment handler (#103) (Wednesday, 15 February)
• Re: [w3c/webpayments-method-identifiers] Circular dependency between PMI and PR specs (#22) (Monday, 13 February)
• Re: [w3c/webpayments-method-identifiers] SRI on manifest (#18) (Monday, 13 February)
• [w3c/browser-payment-api] BREAKING CHANGE: s/paymentRequestID/paymentRequestId (closes #414) (#419) (Monday, 13 February)
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Monday, 13 February)
• Re: [w3c/webpayments-payment-apps-api] Recommended payment apps (#74) (Monday, 13 February)
• Re: [w3c/webpayments-payment-apps-api] Recommended payment apps (#74) (Monday, 13 February)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Friday, 10 February)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Friday, 10 February)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Friday, 10 February)
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Friday, 10 February)
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Friday, 10 February)
• Re: [w3c/browser-payment-api] Update the shippingType option to not allow invalid strings (#416) (Friday, 10 February)
• Re: [w3c/browser-payment-api] Why is the "shippingType" member of PaymentOptions not a PaymentShippingType? (#337) (Friday, 10 February)
• Re: [w3c/browser-payment-api] Update the shippingType option to not allow invalid strings (#416) (Friday, 10 February)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Friday, 10 February)
• Re: [w3c/browser-payment-api] paymentRequestID is spelled wrong :( (#414) (Friday, 10 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Friday, 10 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Thursday, 9 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Thursday, 9 February)
• Re: [w3c/browser-payment-api] paymentRequestID is spelled wrong :( (#414) (Thursday, 9 February)
• Re: [w3c/browser-payment-api] paymentRequestID is spelled wrong :( (#414) (Thursday, 9 February)
• Re: [w3c/browser-payment-api] paymentRequestID is spelled wrong :( (#414) (Thursday, 9 February)
• Re: [w3c/browser-payment-api] paymentRequestID is spelled wrong :( (#414) (Thursday, 9 February)
• Re: [w3c/browser-payment-api] updateWith will silently ignore data in hard-to-debug ways (#350) (Wednesday, 8 February)
• Re: [w3c/browser-payment-api] Introduction is aspirational, but misleading (#410) (Wednesday, 8 February)
• Re: [w3c/browser-payment-api] editorial(intro): drop hyperbolic statements (closes #410) (#411) (Wednesday, 8 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Wednesday, 8 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 8 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 8 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 8 February)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Wednesday, 8 February)
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) (Wednesday, 8 February)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 7 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Monday, 6 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Monday, 6 February)
• [w3c/browser-payment-api] editorial(intro): drop hyperbolic statements (closes #410) (#411) (Monday, 6 February)
• Re: [w3c/browser-payment-api] Introduction is aspirational, but misleading (#410) (Monday, 6 February)
• [w3c/browser-payment-api] Introduction is aspirational, but misleading (#410) (Monday, 6 February)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 3 February)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 1 February)

Michael[tm] Smith

• [w3c/browser-payment-api] Fix markup errors that broke autopublishing (#444) (Tuesday, 28 February)

Molly Dalton

• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Wednesday, 22 February)
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Saturday, 18 February)

Nick Schonning

• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Wednesday, 22 February)

Nick Shearer

• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 7 February)

Rouslan Solomakhin

• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] `country` vs `sortingCode` (#434) (Thursday, 23 February)
• Re: [w3c/browser-payment-api] put request id in details dictionary (#426) (Wednesday, 22 February)
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Tuesday, 21 February)
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Tuesday, 21 February)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 14 February)
• Re: [w3c/browser-payment-api] Define payment option filtering algorithm. (#420) (Tuesday, 14 February)
• [w3c/browser-payment-api] Define payment option filtering algorithm. (#420) (Tuesday, 14 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Tuesday, 7 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Tuesday, 7 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Tuesday, 7 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Tuesday, 7 February)
• Re: [w3c/browser-payment-api] PaymentRequestID initialization (#412) (Tuesday, 7 February)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 1 February)

rvm4

• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Wednesday, 22 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Wednesday, 22 February)
• [w3c/browser-payment-api] put request id in details dictionary (#426) (Wednesday, 22 February)
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Wednesday, 22 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Tuesday, 21 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Thursday, 9 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Thursday, 9 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Wednesday, 8 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Wednesday, 8 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Tuesday, 7 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Tuesday, 7 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Tuesday, 7 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Tuesday, 7 February)
• [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Tuesday, 7 February)
• Re: [w3c/browser-payment-api] PaymentRequestID initialization (#412) (Tuesday, 7 February)
• [w3c/browser-payment-api] PaymentRequestID initialization (#412) (Tuesday, 7 February)

Salvador de la Puente González

• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Wednesday, 22 February)

Simon Pieters

• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) (Monday, 20 February)
• Re: [w3c/browser-payment-api] editorial: s/character/code unit/ (closes #322) (#421) (Friday, 17 February)
• Re: [w3c/browser-payment-api] editorial: s/character/code point/ (closes #322) (#421) (Thursday, 16 February)
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Monday, 13 February)
• Re: [w3c/browser-payment-api] BREAKING CHANGE: s/paymentRequestID/paymentRequestId (closes #414) (#419) (Monday, 13 February)

Tobie Langel

• [w3c/browser-payment-api] Create pr-preview config file. (#445) (Tuesday, 28 February)

Tommy Thorsen

• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Tuesday, 28 February)
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Tuesday, 28 February)
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Tuesday, 28 February)
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) (Wednesday, 22 February)
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) (Wednesday, 22 February)
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Tuesday, 21 February)
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Tuesday, 21 February)
• [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Tuesday, 21 February)
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) (Tuesday, 21 February)
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) (Monday, 20 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 17 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Thursday, 16 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Thursday, 16 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Thursday, 16 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Thursday, 16 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Thursday, 16 February)
• Re: [w3c/webpayments-payment-apps-api] Recommended payment apps (#74) (Friday, 10 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 8 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 7 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 7 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 7 February)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Monday, 6 February)
• Re: [w3c/webpayments-payment-apps-api] Recovery of a failed Push Payment (#102) (Friday, 3 February)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 3 February)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 3 February)
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) (Friday, 3 February)
• [w3c/webpayments-payment-apps-api] Simplify Example 3 as per issue #82 (#101) (Friday, 3 February)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Friday, 3 February)

Zach Koch

• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Friday, 17 February)
• Re: [w3c/browser-payment-api] Take paymentRequestID in constructor (#413) (Thursday, 9 February)
• Re: [w3c/browser-payment-api] Why is the "shippingType" member of PaymentOptions not a PaymentShippingType? (#337) (Thursday, 9 February)
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Thursday, 9 February)

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