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

adamroach

• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Monday, 30 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Thursday, 26 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Thursday, 26 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Thursday, 26 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Thursday, 26 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) (Tuesday, 24 January)
• [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Monday, 23 January)
• [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Monday, 23 January)
• [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) (Monday, 23 January)
• [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Monday, 23 January)
• [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Monday, 23 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Monday, 23 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Sunday, 22 January)
• Re: [w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83) (Tuesday, 17 January)
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) (Tuesday, 10 January)
• Re: [w3c/webpayments-payment-apps-api] Lambda functions for app matching (#76) (Wednesday, 4 January)

Ade Bateman

• Re: [w3c/browser-payment-api] Invoke "allowed to use" always (#383) (Wednesday, 11 January)
• Re: [w3c/browser-payment-api] style(index.html): cleanup markup (#392) (Wednesday, 11 January)
• Re: [w3c/browser-payment-api] fix(payment request algo): set attributes to null if not given (closes #385) (#391) (Wednesday, 11 January)
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) (Wednesday, 11 January)
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) (Thursday, 5 January)
• Re: [w3c/browser-payment-api] Various fixes to the PaymentRequest constructor (#374) (Wednesday, 4 January)
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) (Wednesday, 4 January)

Adrian Hope-Bailie

• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Friday, 27 January)
• [w3c/webpayments-method-identifiers] Changes to address Action #40 (#21) (Thursday, 26 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 24 January)
• Re: [w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19) (Monday, 23 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Sunday, 22 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Sunday, 22 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Sunday, 22 January)
• Re: [w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19) (Sunday, 22 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Sunday, 22 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Sunday, 22 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 20 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 20 January)
• Re: [w3c/webpayments-payment-apps-api] Small fixes + displayItems (#88) (Tuesday, 17 January)
• Re: [w3c/webpayments-payment-apps-api] Updates around display of windows (#89) (Tuesday, 17 January)

Conor Hackett

• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83) (Monday, 23 January)
• Re: [w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83) (Monday, 23 January)
• [w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83) (Tuesday, 10 January)

Dave Longley

• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 27 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 27 January)
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Friday, 27 January)
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Friday, 27 January)
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) (Monday, 23 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Monday, 23 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Friday, 20 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Friday, 20 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] waitForUpdate is not defined (#371) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Tuesday, 17 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Tuesday, 17 January)
• Re: [w3c/webpayments-payment-apps-api] Introduce the PaymentAppResponseData dictionary (#84) (Thursday, 12 January)
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) (Tuesday, 10 January)

Domenic Denicola

• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Thursday, 26 January)
• Re: [w3c/browser-payment-api] Move state transitions diagram into a note (#406) (Monday, 23 January)
• Re: [w3c/browser-payment-api] Move state transitions diagram into a note (#406) (Monday, 23 January)
• Re: [w3c/browser-payment-api] Queue tasks to change developer-visible properties (#405) (Saturday, 21 January)
• Re: [w3c/browser-payment-api] Need to define the interaction of payment API with navigation and browsing context destruction (#360) (Saturday, 21 January)
• [w3c/browser-payment-api] Define [[waitForUpdate]] and make it clear where it lives (#407) (Friday, 20 January)
• Re: [w3c/browser-payment-api] waitForUpdate is not defined (#371) (Friday, 20 January)
• Re: [w3c/browser-payment-api] Why is the "shippingType" member of PaymentOptions not a PaymentShippingType? (#337) (Friday, 20 January)
• [w3c/browser-payment-api] Move state transitions diagram into a note (#406) (Friday, 20 January)
• [w3c/browser-payment-api] Queue tasks to change developer-visible properties (#405) (Friday, 20 January)
• [w3c/browser-payment-api] State how payment details modifier data is serialized and used (#404) (Friday, 20 January)
• Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) (Friday, 20 January)
• Re: [w3c/browser-payment-api] waitForUpdate is not defined (#371) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: don't capitalize RFC 2119 terms (#377) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Wednesday, 18 January)
• [w3c/browser-payment-api] Editorial: firing an event is not done correctly (#401) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] Drop redundant reference to secure context + other redefinitions (#399) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) (Monday, 16 January)
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) (Monday, 16 January)
• Re: [w3c/browser-payment-api] The "data" member of PaymentDetailsModifier doesn't seem to be used for anything (#346) (Saturday, 14 January)
• Re: [w3c/browser-payment-api] fix(payment request algo): set attributes to null if not given (closes #385) (#391) (Saturday, 14 January)
• [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) (Saturday, 14 January)
• Re: [w3c/browser-payment-api] style(index.html): cleanup markup (#392) (Saturday, 14 January)
• Re: [w3c/browser-payment-api] Internal slots vs. attributes (#393) (Wednesday, 11 January)
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) (Wednesday, 11 January)
• [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] fix(payment request algo): set attributes to null if not given (closes #385) (#391) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Add canMakePayment() method (#380) (Thursday, 5 January)
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) (Thursday, 5 January)
• Re: [w3c/browser-payment-api] "contains a value for" isn't defined for dictionaries (#321) (Thursday, 5 January)
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) (Wednesday, 4 January)

ianbjacobs

• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Monday, 30 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Monday, 30 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 27 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 27 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 27 January)
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Thursday, 26 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Thursday, 26 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Add sentence on display of payment app origin (#100) (Tuesday, 24 January)
• [w3c/webpayments-payment-apps-api] Add sentence on display of payment app origin (#100) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 24 January)
• Re: [w3c/browser-payment-api] Is 'currencySystem' required? (#408) (Monday, 23 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Monday, 23 January)
• Re: [w3c/browser-payment-api] Why is the "shippingType" member of PaymentOptions not a PaymentShippingType? (#337) (Saturday, 21 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Friday, 20 January)
• Re: [w3c/webpayments-payment-apps-api] * updates around payment app registration, more clarity wrt user cons… (#93) (Friday, 20 January)
• [w3c/webpayments-payment-apps-api] * updates around payment app registration, more clarity wrt user cons… (#93) (Friday, 20 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Friday, 20 January)
• Re: [w3c/webpayments-methods-card] Fix typo stating BasicCardRequest as BasicCardResponse (#24) (Friday, 20 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) (Wednesday, 18 January)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Wednesday, 18 January)
• Re: [w3c/webpayments-payment-apps-api] Clarification on Payment App "Options" (#90) (Wednesday, 18 January)
• Re: [w3c/webpayments-payment-apps-api] Updates around display of windows (#89) (Tuesday, 17 January)
• Re: [w3c/webpayments-payment-apps-api] Small fixes + displayItems (#88) (Tuesday, 17 January)
• Re: [w3c/webpayments-payment-apps-api] Small fixes + displayItems (#88) (Tuesday, 17 January)
• [w3c/webpayments-payment-apps-api] Updates around display of windows (#89) (Tuesday, 17 January)
• [w3c/webpayments-payment-apps-api] Small fixes + displayItems (#88) (Tuesday, 17 January)
• Re: [w3c/webpayments-payment-apps-api] We need a PaymentAppResponseData dictionary (#81) (Tuesday, 17 January)
• Re: [w3c/webpayments-payment-apps-api] We need a PaymentAppResponseData dictionary (#81) (Tuesday, 17 January)
• Re: [w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83) (Tuesday, 17 January)
• Re: [w3c/webpayments-payment-apps-api] Introduce the PaymentAppResponseData dictionary (#84) (Tuesday, 17 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Tuesday, 17 January)
• Re: [w3c/webpayments-payment-apps-api] Security note adjustment (#87) (Friday, 13 January)
• [w3c/webpayments-payment-apps-api] Security note adjustment (#87) (Friday, 13 January)
• Re: [w3c/webpayments-payment-apps-api] Move secure context note from intro to where the requirement is listed. (#85) (Friday, 13 January)
• Re: [w3c/webpayments-payment-apps-api] Move secure context note from intro to where the requirement is listed. (#85) (Friday, 13 January)
• Re: [w3c/webpayments-payment-apps-api] security note moved (#86) (Friday, 13 January)
• Re: [w3c/webpayments-payment-apps-api] Move secure context note from intro to where the requirement is listed. (#85) (Friday, 13 January)
• Re: [w3c/webpayments-payment-apps-api] Move secure context note from intro to where the requirement is listed. (#85) (Friday, 13 January)
• [w3c/webpayments-payment-apps-api] security note moved (#86) (Friday, 13 January)
• Re: [w3c/webpayments-payment-apps-api] Edits based on recent discussions and decisions (#80) (Friday, 13 January)
• Re: [w3c/webpayments-payment-apps-api] Edits based on recent discussions and decisions (#80) (Friday, 13 January)
• Re: [w3c/webpayments-payment-apps-api] Edits based on recent discussions and decisions (#80) (Friday, 13 January)
• Re: [w3c/webpayments-payment-apps-api] We need a PaymentAppResponseData dictionary (#81) (Friday, 13 January)
• [w3c/webpayments-payment-apps-api] Move secure context note from intro to where the requirement is listed. (#85) (Thursday, 12 January)
• Re: [w3c/webpayments-payment-apps-api] Edits based on recent discussions and decisions (#80) (Thursday, 12 January)
• Re: [w3c/webpayments-payment-apps-api] How does the payee provide information about recommended payment apps? (#79) (Thursday, 12 January)
• Re: [w3c/webpayments-payment-apps-api] Introduce the PaymentAppResponseData dictionary (#84) (Thursday, 12 January)
• Re: [w3c/webpayments-payment-apps-api] How does the payee provide information about recommended payment apps? (#79) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Providing/Generating paymentRequestID during construction (#388) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Providing/Generating paymentRequestID during construction (#388) (Monday, 9 January)
• Re: [w3c/browser-payment-api] Phone number format (#390) (Friday, 6 January)
• Re: [w3c/webpayments-payment-apps-api] What is matching and display behavior for various scenarios of recommended apps, enabled apps, non-enabled apps, etc.? (#38) (Friday, 6 January)
• Re: [w3c/webpayments-payment-apps-api] What is matching and display behavior for various scenarios of recommended apps, enabled apps, non-enabled apps, etc.? (#38) (Friday, 6 January)
• Re: [w3c/webpayments-payment-apps-api] Should we allow payment providers to issue queries about their installed payment apps (match on origin) (#6) (Friday, 6 January)
• Re: [w3c/webpayments-payment-apps-api] Should we allow payment providers to issue queries about their installed payment apps (match on origin) (#6) (Friday, 6 January)
• Re: [w3c/webpayments-payment-apps-api] Versioning (#45) (Friday, 6 January)
• Re: [w3c/webpayments-payment-apps-api] Versioning (#45) (Friday, 6 January)
• Re: [w3c/webpayments-payment-apps-api] Section 6 steps 1-5 seem to avoid selecting a payment option / payment method (#56) (Friday, 6 January)
• Re: [w3c/webpayments-payment-apps-api] Section 6 steps 1-5 seem to avoid selecting a payment option / payment method (#56) (Friday, 6 January)
• [w3c/webpayments-payment-apps-api] Edits based on recent discussions and decisions (#80) (Thursday, 5 January)
• [w3c/webpayments-payment-apps-api] How does the payee provide information about recommended payment apps? (#79) (Thursday, 5 January)
• Re: [w3c/webpayments-payment-apps-api] Split out enabled and supported methods (#7) (Thursday, 5 January)
• Re: [w3c/webpayments-payment-apps-api] Split out enabled and supported methods (#7) (Thursday, 5 January)
• Re: [w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63) (Thursday, 5 January)
• Re: [w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63) (Thursday, 5 January)
• Re: [w3c/webpayments-method-identifiers] Why are payment ids restricted to [a-z0-9]? (#20) (Thursday, 5 January)
• Re: [w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19) (Thursday, 5 January)
• Re: [w3c/browser-payment-api] Invoke "allowed to use" always (#383) (Thursday, 5 January)
• Re: [w3c/webpayments-payment-apps-api] Suggested apps (#74) (Wednesday, 4 January)
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) (Wednesday, 4 January)
• Re: [w3c/webpayments-payment-apps-api] (Deleted this edit by mistake before merged) (#78) (Wednesday, 4 January)
• Re: [w3c/webpayments-payment-apps-api] Lambda functions for app matching (#76) (Wednesday, 4 January)
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) (Tuesday, 3 January)
• Re: [w3c/browser-payment-api] PaymentRequest does not handle the case of store pickup (#389) (Tuesday, 3 January)

Jake Archibald

• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Monday, 30 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Thursday, 26 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Thursday, 26 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Thursday, 26 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Monday, 23 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Monday, 23 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Sunday, 22 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Sunday, 22 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Sunday, 22 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Sunday, 22 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 20 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Tuesday, 17 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Tuesday, 17 January)

Jeff Burdges

• Re: [w3c/browser-payment-api] Add canMakePayment() method (#380) (Thursday, 5 January)
• Re: [w3c/browser-payment-api] Add canMakePayment() method (#380) (Thursday, 5 January)

Jenan Wise

• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) (Wednesday, 18 January)
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) (Tuesday, 3 January)

Jinho Bang

• Re: [w3c/browser-payment-api] Is 'currencySystem' required? (#408) (Monday, 23 January)

Manu Sporny

• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Monday, 23 January)

Marcos Cáceres

• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 31 January)
• Re: [w3c/browser-payment-api] Is 'currencySystem' required? (#408) (Monday, 30 January)
• Re: [w3c/browser-payment-api] Move state transitions diagram into a note (#406) (Monday, 30 January)
• Re: [w3c/browser-payment-api] Is section 3.4 informative or normative? (#342) (Monday, 30 January)
• Re: [w3c/browser-payment-api] Move state transitions diagram into a note (#406) (Monday, 30 January)
• Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23) (Monday, 30 January)
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) (Monday, 30 January)
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) (Monday, 30 January)
• Re: [w3c/browser-payment-api] Providing/Generating paymentRequestID during construction (#388) (Monday, 30 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Friday, 27 January)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Friday, 27 January)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Friday, 27 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 27 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 27 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 27 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Friday, 27 January)
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Friday, 27 January)
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) (Wednesday, 25 January)
• Re: [w3c/browser-payment-api] The "data" member of PaymentDetailsModifier doesn't seem to be used for anything (#346) (Wednesday, 25 January)
• Re: [w3c/browser-payment-api] State how payment details modifier data is serialized and used (#404) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 24 January)
• [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 24 January)
• Re: [w3c/browser-payment-api] Move state transitions diagram into a note (#406) (Monday, 23 January)
• Re: [w3c/browser-payment-api] State how payment details modifier data is serialized and used (#404) (Monday, 23 January)
• Re: [w3c/browser-payment-api] Define [[waitForUpdate]] and make it clear where it lives (#407) (Monday, 23 January)
• Re: [w3c/browser-payment-api] waitForUpdate is not defined (#371) (Monday, 23 January)
• Re: [w3c/browser-payment-api] Move state transitions diagram into a note (#406) (Monday, 23 January)
• Re: [w3c/browser-payment-api] State how payment details modifier data is serialized and used (#404) (Monday, 23 January)
• Re: [w3c/browser-payment-api] State how payment details modifier data is serialized and used (#404) (Monday, 23 January)
• Re: [w3c/browser-payment-api] Setting internal slots of objects from asynchronous steps is not OK (#339) (Monday, 23 January)
• Re: [w3c/browser-payment-api] The shipping address/option changed algorithms should not be synchronously poking internal slots (#351) (Monday, 23 January)
• Re: [w3c/browser-payment-api] Is it intended that abort() rejects the acceptPromise and resolves its return value in separate tasks? (#340) (Monday, 23 January)
• Re: [w3c/browser-payment-api] Queue tasks to change developer-visible properties (#405) (Monday, 23 January)
• Re: [w3c/browser-payment-api] Queue tasks to change developer-visible properties (#405) (Monday, 23 January)
• Re: [w3c/browser-payment-api] Define [[waitForUpdate]] and make it clear where it lives (#407) (Saturday, 21 January)
• Re: [w3c/browser-payment-api] Queue tasks to change developer-visible properties (#405) (Saturday, 21 January)
• Re: [w3c/browser-payment-api] Queue tasks to change developer-visible properties (#405) (Saturday, 21 January)
• Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) (Friday, 20 January)
• Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) (Friday, 20 January)
• Re: [w3c/browser-payment-api] canHandlePayment() might be in the wrong place? (#403) (Friday, 20 January)
• [w3c/browser-payment-api] canHandlePayment() might be in the wrong place? (#403) (Friday, 20 January)
• Re: [w3c/webpayments-methods-card] Fix typo stating BasicCardRequest as BasicCardResponse (#24) (Friday, 20 January)
• Re: [w3c/webpayments-methods-card] Fix typo stating BasicCardRequest as BasicCardResponse (#24) (Friday, 20 January)
• Re: [w3c/webpayments-methods-card] Fix typo stating BasicCardRequest as BasicCardResponse (#24) (Friday, 20 January)
• Re: [w3c/browser-payment-api] Editorial: don't capitalize RFC 2119 terms (#377) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Phone number format (#390) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] feat(payment resp algo): phone# SHOULD be E.164 (closes #390) (#396) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses for clarity, and spell out their params in their definition (#378) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] Remove confusing IDL comments (#395) (Wednesday, 18 January)
• [w3c/browser-payment-api] Editorial: Add missing xrefs to various specs (#400) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (#375) (Wednesday, 18 January)
• [w3c/browser-payment-api] Drop redundant reference to secure context + other redefinitions (#399) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] DOMExceptions are now in WebIDL (#314) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] DOMExceptions are now in WebIDL (#314) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Wednesday, 18 January)
• [w3c/browser-payment-api] Editorial: refer to methods with parentheses (closes #378) (#398) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] Editorial: don't capitalize RFC 2119 terms (#377) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] Editorial: refer to methods with parentheses for clarity, and spell out their params in their definition (#378) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] feat(payment resp algo): phone# SHOULD be E.164 (closes #390) (#396) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) (Wednesday, 18 January)
• [w3c/browser-payment-api] Editorial: use new language for DOMExceptions (close #375) (#397) (Wednesday, 18 January)
• [w3c/browser-payment-api] feat(payment resp algo): phone# SHOULD be E.164 (closes #390) (#396) (Tuesday, 17 January)
• [w3c/browser-payment-api] Remove confusing IDL comments (#395) (Tuesday, 17 January)
• Re: [w3c/browser-payment-api] Internal slots vs. attributes (#393) (Tuesday, 17 January)
• Re: [w3c/browser-payment-api] Internal slots vs. attributes (#393) (Tuesday, 17 January)
• Re: [w3c/webpayments-method-identifiers] SRI on manifest (#18) (Tuesday, 17 January)
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) (Monday, 16 January)
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) (Monday, 16 January)
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) (Monday, 16 January)
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) (Monday, 16 January)
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) (Monday, 16 January)
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) (Monday, 16 January)
• Re: [w3c/browser-payment-api] Internal slots vs. attributes (#393) (Monday, 16 January)
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) (Sunday, 15 January)
• Re: [w3c/browser-payment-api] fix(payment request algo): set attributes to null if not given (closes #385) (#391) (Sunday, 15 January)
• Re: [w3c/browser-payment-api] fix(payment request algo): set attributes to null if not given (closes #385) (#391) (Saturday, 14 January)
• Re: [w3c/browser-payment-api] style(index.html): cleanup markup (#392) (Saturday, 14 January)
• Re: [w3c/browser-payment-api] style(index.html): cleanup markup (#392) (Saturday, 14 January)
• [w3c/browser-payment-api] style(index.html): cleanup markup (#392) (Tuesday, 10 January)
• [w3c/browser-payment-api] fix(payment request algo): set attributes to null if not given (closes #385) (#391) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Serializer behavior (#385) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Providing/Generating paymentRequestID during construction (#388) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Providing/Generating paymentRequestID during construction (#388) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Examples in the spec (#274) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Examples in the spec (#274) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Phone number format (#390) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Invoke "allowed to use" always (#383) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Invoke "allowed to use" always (#383) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Providing/Generating paymentRequestID during construction (#388) (Monday, 9 January)
• Re: [w3c/browser-payment-api] an event to providing standards for push payment methods (#223) (Wednesday, 4 January)
• Re: [w3c/browser-payment-api] an event to providing standards for push payment methods (#223) (Wednesday, 4 January)
• Re: [w3c/browser-payment-api] Add `enableLegacyCheckout` option to PaymentOptions. (#365) (Wednesday, 4 January)
• Re: [w3c/browser-payment-api] Add `enableLegacyCheckout` option to PaymentOptions. (#365) (Wednesday, 4 January)
• Re: [w3c/browser-payment-api] A PaymentDetailsModifier may not have an additionalDisplayItems value present (#335) (Wednesday, 4 January)
• Re: [w3c/browser-payment-api] Various fixes to the PaymentRequest constructor (#374) (Wednesday, 4 January)
• Re: [w3c/browser-payment-api] PaymentRequest constructor validation ordering does not match Blink at all (#373) (Wednesday, 4 January)
• Re: [w3c/browser-payment-api] A `PaymentItem` can't be a "valid decimal monetary value" (#334) (Wednesday, 4 January)
• Re: [w3c/browser-payment-api] PaymentDetails may not have values present for various sequences, but the PaymentRequest constructor assumes that it does (#333) (Wednesday, 4 January)

Mark Nottingham

• Re: [w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19) (Tuesday, 17 January)

Mathieu Perreault

• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Tuesday, 24 January)

Michael[tm] Smith

• Re: [w3c/browser-payment-api] "contains a value for" isn't defined for dictionaries (#321) (Thursday, 5 January)
• Re: [w3c/browser-payment-api] "contains a value for" isn't defined for dictionaries (#321) (Thursday, 5 January)

Nick Shearer

• Re: [w3c/browser-payment-api] Phone number format (#390) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Phone number format (#390) (Friday, 6 January)

ockxdd

• Re: [w3c/browser-payment-api] Invoke "allowed to use" always (#383) (Friday, 6 January)

Rouslan Solomakhin

• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 31 January)
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Thursday, 26 January)
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Thursday, 26 January)
• [w3c/browser-payment-api] Is 'currencySystem' required? (#408) (Monday, 23 January)
• Re: [w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19) (Monday, 23 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Friday, 20 January)
• Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) (Friday, 20 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 20 January)
• Re: [w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19) (Friday, 20 January)
• [w3c/browser-payment-api] `PaymentInstrument.complete(result)` wording (#402) (Thursday, 19 January)
• Re: [w3c/browser-payment-api] feat(payment resp algo): phone# SHOULD be E.164 (closes #390) (#396) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] The "data" member of PaymentDetailsModifier doesn't seem to be used for anything (#346) (Monday, 16 January)
• Re: [w3c/webpayments-payment-apps-api] payment-manifest.json and canHandle function (#83) (Wednesday, 11 January)
• Re: [w3c/browser-payment-api] Providing/Generating paymentRequestID during construction (#388) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Phone number format (#390) (Tuesday, 10 January)
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) (Tuesday, 10 January)
• Re: [w3c/browser-payment-api] Serializer behavior (#385) (Tuesday, 10 January)
• [w3c/browser-payment-api] Phone number format (#390) (Friday, 6 January)
• Re: [w3c/browser-payment-api] PaymentRequest does not handle the case of store pickup (#389) (Tuesday, 3 January)
• Re: [w3c/browser-payment-api] PaymentRequest does not handle the case of store pickup (#389) (Tuesday, 3 January)

rvm4

• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Tuesday, 31 January)
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Thursday, 26 January)
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Thursday, 26 January)
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Thursday, 26 January)
• [w3c/browser-payment-api] Add billing shipping type (#409) (Thursday, 26 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Friday, 20 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Thursday, 19 January)
• [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Wednesday, 18 January)

Salvador de la Puente González

• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Saturday, 28 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Saturday, 28 January)

sanjoypal

• [w3c/browser-payment-api] PaymentRequest does not handle the case of store pickup (#389) (Tuesday, 3 January)
• [w3c/browser-payment-api] Providing paymentRequestID during construction (#388) (Tuesday, 3 January)

Simon Pieters

• Re: [w3c/browser-payment-api] Invoke "allowed to use" always (#383) (Thursday, 5 January)

stevenatkin

• [w3c/webpayments-method-identifiers] Why are payment ids restricted to [a-z0-9]? (#20) (Thursday, 5 January)

Tobie Langel

• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) (Monday, 16 January)
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) (Monday, 16 January)
• Re: [w3c/browser-payment-api] [WebIDL] reference is wrong (#394) (Monday, 16 January)

Tommy Thorsen

• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Tuesday, 31 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 27 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Thursday, 26 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Thursday, 26 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Wednesday, 25 January)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Tuesday, 24 January)
• Re: [w3c/browser-payment-api] Is 'currencySystem' required? (#408) (Monday, 23 January)
• Re: [w3c/webpayments-payment-apps-api] Payment App Decline (#92) (Thursday, 19 January)
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) (Tuesday, 17 January)
• Re: [w3c/webpayments-payment-apps-api] Introduce the PaymentAppResponseData dictionary (#84) (Thursday, 12 January)
• Re: [w3c/webpayments-payment-apps-api] We need a PaymentAppResponseData dictionary (#81) (Thursday, 12 January)
• [w3c/webpayments-payment-apps-api] Introduce the PaymentAppResponseData dictionary (#84) (Thursday, 12 January)
• Re: [w3c/browser-payment-api] Internal slots vs. attributes (#393) (Thursday, 12 January)
• Re: [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) (Tuesday, 10 January)
• [w3c/browser-payment-api] Internal slots vs. attributes (#393) (Tuesday, 10 January)
• Re: [w3c/webpayments-payment-apps-api] We need a PaymentAppResponseData dictionary (#81) (Tuesday, 10 January)
• [w3c/webpayments-payment-apps-api] Example 3 does not work (#82) (Tuesday, 10 January)
• [w3c/webpayments-payment-apps-api] We need a PaymentAppResponseData dictionary (#81) (Tuesday, 10 January)

Tri Nguyen

• [w3c/webpayments-methods-card] Fix typo stating BasicCardRequest as BasicCardResponse (#24) (Thursday, 19 January)

Zach Koch

• Re: [w3c/browser-payment-api] `PaymentInstrument.complete(result)` wording (#402) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 24 January)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 24 January)
• [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Wednesday, 18 January)
• Re: [w3c/webpayments-payment-apps-api] Clarification on Payment App "Options" (#90) (Wednesday, 18 January)
• [w3c/webpayments-payment-apps-api] Clarification on Payment App "Options" (#90) (Wednesday, 18 January)
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) (Wednesday, 11 January)
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) (Wednesday, 11 January)
• Re: [w3c/browser-payment-api] Invoke "allowed to use" always (#383) (Wednesday, 11 January)
• Re: [w3c/browser-payment-api] Security hole in payment API when a constructor from a no longer active document is invoked (#361) (Wednesday, 11 January)
• Re: [w3c/browser-payment-api] fix(payment request algo): set attributes to null if not given (closes #385) (#391) (Wednesday, 11 January)
• Re: [w3c/browser-payment-api] Ambiguous conformance requirement in constructor (#354) (Wednesday, 11 January)
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) (Wednesday, 11 January)
• Re: [w3c/browser-payment-api] The "data" member of PaymentMethodData doesn't seem to actually be used for anything (#338) (Wednesday, 11 January)
• Re: [w3c/browser-payment-api] Straighten out the payment method data flow (#382) (Wednesday, 11 January)

Last message date: Tuesday, 31 January 2017 23:51:40 UTC