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

adamroach

• Re: [w3c/webpayments-payment-apps-api] `appRequest` attribute should not be a dictionary (#111) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] `appRequest` attribute should not be a dictionary (#111) (Monday, 20 March)
• Re: [w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109) (Monday, 20 March)
• Re: [w3c/webpayments-payment-apps-api] Per 16 March teleconf [1], displayItems are not handed to the payment app (#110) (Sunday, 19 March)
• Re: [w3c/webpayments-payment-apps-api] Per 16 March teleconf [1], displayItems are not handed to the payment app (#110) (Sunday, 19 March)
• [w3c/webpayments-payment-apps-api] Updates for F2F meeting (#113) (Saturday, 18 March)
• Re: [w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109) (Saturday, 18 March)
• Re: [w3c/webpayments-payment-apps-api] `appRequest` attribute should not be a dictionary (#111) (Friday, 17 March)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Friday, 17 March)
• Re: [w3c/webpayments-payment-apps-api] Merging from main branch (#112) (Friday, 17 March)
• [w3c/webpayments-payment-apps-api] Merging from main branch (#112) (Friday, 17 March)

Addison Phillips

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

Adrian Hope-Bailie

• Re: [w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109) (Thursday, 16 March)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Thursday, 16 March)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Thursday, 16 March)
• Re: [w3c/browser-payment-api] Define payment option filtering algorithm. (#420) (Thursday, 16 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Wednesday, 15 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] PaymentRequest does not handle the case of store pickup (#389) (Tuesday, 14 March)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Thursday, 9 March)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Wednesday, 8 March)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Wednesday, 8 March)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Wednesday, 8 March)
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) (Tuesday, 7 March)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Tuesday, 7 March)
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) (Monday, 6 March)
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Wednesday, 1 March)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Tuesday, 28 February)

Alexander Batishchev

• [w3c/browser-payment-api] Adding legal entity types for consistency (#491) (Friday, 31 March)

Anders Rundgren

• Re: [w3c/browser-payment-api] complete() does not match all payment apps (#484) (Wednesday, 29 March)
• [w3c/browser-payment-api] complete() does not match all payment apps (#484) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] API assumes Issuer communication is OOB (#447) (Friday, 3 March)
• Re: [w3c/browser-payment-api] API assumes Issuer communication is OOB (#447) (Friday, 3 March)
• [w3c/browser-payment-api] API assumes Issuer communication is OOB (#447) (Friday, 3 March)

Anne van Kesteren

• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Tuesday, 14 March)

Ben Tian

• Re: [w3c/browser-payment-api] API assumes Issuer communication is OOB (#447) (Friday, 3 March)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Wednesday, 1 March)

Boris Zbarsky

• Re: [w3c/browser-payment-api] Need to define the interaction of payment API with navigation and browsing context destruction (#360) (Saturday, 18 March)

chaals

• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] Section for A11Y Considerations (#450) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] Section for A11Y Considerations (#450) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] Section for A11Y Considerations (#450) (Wednesday, 8 March)

Dave Longley

• Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Wednesday, 29 March)
• Re: [w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120) (Wednesday, 29 March)
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) (Friday, 17 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Friday, 17 March)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Wednesday, 8 March)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Wednesday, 8 March)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Tuesday, 7 March)
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) (Tuesday, 7 March)

Domenic Denicola

• Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Friday, 31 March)
• Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Friday, 31 March)
• Re: [w3c/browser-payment-api] Unclear what happens when multiple PRs call show() (#462) (Friday, 31 March)
• Re: [w3c/browser-payment-api] Disallow multiple showing payment requests per user agent (#487) (Friday, 31 March)
• Re: [w3c/browser-payment-api] fix: change Events section to normative (closes #466) (#489) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] fix: change Events section to normative (closes #466) (#489) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] fix: change Events section to normative (closes #466) (#489) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] fix: change Events section to normative (closes #466) (#489) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] fix: change Events section to normative (closes #466) (#489) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] fix: change Events section to normative (closes #466) (#489) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] fix: change Events section to normative (closes #466) (#489) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] Behavior for multiple modifiers for the same payment method is not defined (#309) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] Why are two sections non-normative? (#466) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] Why are two sections non-normative? (#466) (Thursday, 30 March)
• [w3c/browser-payment-api] Use "NotAllowedError" instead of "QuotaExceededError" (#488) (Thursday, 30 March)
• [w3c/browser-payment-api] Disallow multiple showing payment requests per user agent (#487) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] Unclear what happens when multiple PRs call show() (#462) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] Supplement QuoteExceededError with NotAllowedError for canMakePayments (#485) (Wednesday, 29 March)
• Re: [w3c/browser-payment-api] Unclear what happens when multiple PRs call show() (#462) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Should the user agent generate the `id` when it's empty? (#483) (Monday, 27 March)
• Re: [w3c/browser-payment-api] Unclear what happens when multiple PRs call show() (#462) (Saturday, 25 March)
• Re: [w3c/browser-payment-api] Unclear what happens when multiple PRs call show() (#462) (Thursday, 23 March)
• Re: [w3c/browser-payment-api] editorial: remove redundant event declaration (#469) (Thursday, 23 March)
• Re: [w3c/browser-payment-api] Unclear what happens when multiple PRs call show() (#462) (Thursday, 23 March)
• Re: [w3c/browser-payment-api] supportedMethods (URL and enums) (#464) (Monday, 20 March)
• Re: [w3c/browser-payment-api] supportedMethods (URL and enums) (#464) (Monday, 20 March)
• Re: [w3c/browser-payment-api] Ambiguity in "Process payment methods:" (#458) (Thursday, 16 March)
• Re: [w3c/browser-payment-api] NotSupportedError in private browsing mode (#448) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] NotSupportedError in private browsing mode (#448) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] maybe add `DisplayItem` dictionary (#457) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] Initial values for internal slots (#436) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Changes to show() and canMakePayment() to take into account (#454) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Changes to show() and canMakePayment() to take into account (#454) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Changes to show() and canMakePayment() to take into account (#454) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Changes to show() and canMakePayment() to take into account (#454) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Fix constructor handling of shippingType (#452) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Fix constructor handling of shippingType (#452) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Fix constructor handling of shippingType (#452) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Fix constructor handling of shippingType (#452) (Thursday, 9 March)
• Re: [w3c/browser-payment-api] Fix constructor handling of shippingType (#452) (Thursday, 9 March)
• Re: [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Thursday, 9 March)
• Re: [w3c/browser-payment-api] Fix constructor handling of shippingType (#452) (Thursday, 9 March)
• [w3c/browser-payment-api] Fix constructor handling of shippingType (#452) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Wednesday, 8 March)
• [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] Specify how to abort a payment request (#449) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Tuesday, 7 March)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Monday, 6 March)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Monday, 6 March)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Monday, 6 March)
• Re: [w3c/browser-payment-api] PaymentDetails "total" member should be required (#320) (Monday, 6 March)
• Re: [w3c/browser-payment-api] PaymentDetails "total" member should be required (#320) (Monday, 6 March)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Monday, 6 March)
• [w3c/browser-payment-api] Specify how to abort a payment request (#449) (Monday, 6 March)
• Re: [w3c/browser-payment-api] NotSupportedError in private browsing mode (#448) (Monday, 6 March)
• Re: [w3c/browser-payment-api] NotSupportedError in private browsing mode (#448) (Monday, 6 March)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Thursday, 2 March)

frank-hoffmann

• [w3c/webpayments-payment-apps-api] Share user data with Payment App (#123) (Friday, 31 March)
• Re: [w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120) (Thursday, 30 March)
• Re: [w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120) (Wednesday, 29 March)
• Re: [w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120) (Wednesday, 29 March)
• [w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120) (Tuesday, 28 March)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Wednesday, 8 March)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Wednesday, 1 March)

ianbjacobs

• Re: [w3c/browser-payment-api] Clarify wording to not imply 'pull' only payments (#474) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Thursday, 30 March)
• Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) (Wednesday, 29 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Wednesday, 29 March)
• Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) (Wednesday, 29 March)
• Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Wednesday, 29 March)
• Re: [w3c/browser-payment-api] complete() does not match all payment apps (#484) (Wednesday, 29 March)
• [w3c/webpayments-payment-apps-api] [Editorial] Clean up respec errors (#122) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Consider removing merchant preference language (#481) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Tuesday, 28 March)
• Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Consider removing merchant preference language (#481) (Friday, 24 March)
• [w3c/browser-payment-api] Does PR API need to include text around matching to take payment method manifest into account? (#478) (Friday, 24 March)
• [w3c/webpayments-payment-apps-api] Relation between merchant order of payment methods and payment app order of instruments (#116) (Thursday, 23 March)
• [w3c/webpayments-methods-card] Clarify this specification is intended to become a W3C Note (#27) (Wednesday, 22 March)
• Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) (Wednesday, 22 March)
• [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] Use PaymentRequest and PaymentResponse (#99) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] Small fixes (#114) (Tuesday, 21 March)
• Re: [w3c/browser-payment-api] Editorial changes (#465) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] Small fixes (#114) (Tuesday, 21 March)
• Re: [w3c/browser-payment-api] Editorial changes (#465) (Tuesday, 21 March)
• Re: [w3c/browser-payment-api] Editorial changes (#465) (Monday, 20 March)
• [w3c/browser-payment-api] Why are two sections non-normative? (#466) (Monday, 20 March)
• [w3c/browser-payment-api] Editorial changes (#465) (Monday, 20 March)
• [w3c/webpayments-payment-apps-api] Small fixes (#114) (Monday, 20 March)
• Re: [w3c/browser-payment-api] supportedMethods (URL and enums) (#464) (Monday, 20 March)
• Re: [w3c/browser-payment-api] supportedMethods (URL and enums) (#464) (Monday, 20 March)
• Re: [w3c/browser-payment-api] supportedMethods (URL and enums) (#464) (Monday, 20 March)
• Re: [w3c/browser-payment-api] supportedMethods (URL and enums) (#464) (Monday, 20 March)
• Re: [w3c/webpayments-method-identifiers] Add marcoscaceres as collaborator (#24) (Monday, 20 March)
• Re: [w3c/webpayments-method-identifiers] Add marcoscaceres as collaborator (#24) (Monday, 20 March)
• Re: [w3c/webpayments-payment-apps-api] Updates for F2F meeting (#113) (Saturday, 18 March)
• Re: [w3c/webpayments-payment-apps-api] Updates for F2F meeting (#113) (Saturday, 18 March)
• [w3c/webpayments-payment-apps-api] Per 16 March teleconf [1], displayItems are not handed to the payment app (#110) (Friday, 17 March)
• Re: [w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109) (Friday, 17 March)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Thursday, 16 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Thursday, 16 March)
• Re: [w3c/browser-payment-api] Define payment option filtering algorithm. (#420) (Thursday, 16 March)
• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Thursday, 16 March)
• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Thursday, 16 March)
• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Thursday, 16 March)
• Re: [w3c/webpayments-payment-apps-api] Run the spec through HTML5-Tidy. (#108) (Wednesday, 15 March)
• Re: [w3c/webpayments-payment-apps-api] Run the spec through HTML5-Tidy. (#108) (Wednesday, 15 March)
• Re: [w3c/webpayments-payment-apps-api] Structural changes based on task force discussion (#107) (Wednesday, 15 March)
• [w3c/webpayments-payment-apps-api] Structural changes based on task force discussion (#107) (Wednesday, 15 March)
• Re: [w3c/webpayments-payment-apps-api] Structural changes based on task force discussion (#107) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Tuesday, 14 March)
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) (Tuesday, 14 March)
• Re: [w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73) (Tuesday, 14 March)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Tuesday, 14 March)
• Re: [w3c/webpayments-payment-apps-api] Replace setManifest()/getManifest() with set()/get()/keys()/has()/delete() (#95) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] Should values for supportedNetworks be defined in Basic Card or separately? (#325) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] Changes to show() and canMakePayment() to take into account (#454) (Friday, 10 March)
• [w3c/browser-payment-api] Changes to show() and canMakePayment() to take into account (#454) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) (Thursday, 9 March)
• Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) (Thursday, 9 March)
• Re: [w3c/webpayments-payment-apps-api] How can we optimize user experience when there is only one match? (#14) (Thursday, 9 March)
• Re: [w3c/webpayments-payment-apps-api] How can we optimize user experience when there is only one match? (#14) (Thursday, 9 March)
• Re: [w3c/webpayments-payment-apps-api] How does the payee provide information about recommended payment apps? (#79) (Thursday, 9 March)
• Re: [w3c/webpayments-payment-apps-api] How does the payee provide information about recommended payment apps? (#79) (Thursday, 9 March)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Thursday, 9 March)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Thursday, 9 March)
• Re: [w3c/browser-payment-api] Section for A11Y Considerations (#450) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] Section for A11Y Considerations (#450) (Wednesday, 8 March)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Wednesday, 8 March)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Tuesday, 7 March)
• Re: [w3c/browser-payment-api] Fix markup errors that broke autopublishing (#444) (Tuesday, 7 March)
• Re: [w3c/browser-payment-api] API assumes Issuer communication is OOB (#447) (Friday, 3 March)
• Re: [w3c/browser-payment-api] API assumes Issuer communication is OOB (#447) (Friday, 3 March)
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Thursday, 2 March)

Jinho Bang

• [w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121) (Tuesday, 28 March)

kayakalan

• Re: [w3c/browser-payment-api] editorial: grouped payment details dictionaries into section (#479) (Friday, 31 March)
• [w3c/browser-payment-api] editorial: grouped payment details dictionaries into section (#479) (Friday, 24 March)

lararennie

• Re: [w3c/browser-payment-api] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Tuesday, 28 March)

Manu Sporny

• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Wednesday, 1 March)

Marcos Caceres

• [w3c/browser-payment-api] mark currencySystem as feature at risk (#482) (Saturday, 25 March)
• [w3c/webpayments-method-identifiers] Check what happens if URL parsing throws.... (#27) (Friday, 24 March)
• [w3c/browser-payment-api] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Friday, 24 March)
• Re: [w3c/browser-payment-api] editorial: grouped payment details dictionaries into section (#479) (Friday, 24 March)
• [w3c/browser-payment-api] Request `shippingType` attribute is not defined (#472) (Thursday, 23 March)
• [w3c/browser-payment-api] editorial: remove redundant event declaration (#469) (Wednesday, 22 March)
• [w3c/browser-payment-api] fix(complete): bugus result value will have thrown already (#468) (Wednesday, 22 March)

Marcos Cáceres

• Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Friday, 31 March)
• Re: [w3c/browser-payment-api] Use "NotAllowedError" instead of "QuotaExceededError" (#488) (Friday, 31 March)
• Re: [w3c/browser-payment-api] editorial: grouped payment details dictionaries into section (#479) (Friday, 31 March)
• Re: [w3c/browser-payment-api] Disallow multiple showing payment requests per user agent (#487) (Friday, 31 March)
• Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Friday, 31 March)
• Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Friday, 31 March)
• Re: [w3c/browser-payment-api] editorial: grouped payment details dictionaries into section (#479) (Friday, 31 March)
• Re: [w3c/browser-payment-api] editorial: grouped payment details dictionaries into section (#479) (Friday, 31 March)
• Re: [w3c/browser-payment-api] Group payment dictionaries into a section (#427) (Friday, 31 March)
• Re: [w3c/browser-payment-api] editorial: grouped payment details dictionaries into section (#479) (Friday, 31 March)
• Re: [w3c/browser-payment-api] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Friday, 31 March)
• Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Friday, 31 March)
• Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Friday, 31 March)
• Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Friday, 31 March)
• Re: [w3c/browser-payment-api] markup issues (#441) (Friday, 31 March)
• Re: [w3c/browser-payment-api] markup issues (#441) (Friday, 31 March)
• Re: [w3c/browser-payment-api] Why are two sections non-normative? (#466) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] fix: change Events section to normative (closes #466) (#489) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] fix: change Events section to normative (closes #466) (#489) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] fix: change Events section to normative (closes #466) (#489) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] fix: change Events section to normative (closes #466) (#489) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] fix: change Events section to normative (closes #466) (#489) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] fix: change Events section to normative (closes #466) (#489) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] fix: change Events section to normative (closes #466) (#489) (Thursday, 30 March)
• [w3c/browser-payment-api] fix: change Events section to normative (closes #466) (#489) (Thursday, 30 March)
• Re: [w3c/browser-payment-api] supportedMethods (URL and DOMString) (#464) (Wednesday, 29 March)
• Re: [w3c/browser-payment-api] Does PR API need to include text around matching to take payment method manifest into account? (#478) (Wednesday, 29 March)
• Re: [w3c/browser-payment-api] Does PR API need to include text around matching to take payment method manifest into account? (#478) (Wednesday, 29 March)
• Re: [w3c/browser-payment-api] Why are two sections non-normative? (#466) (Wednesday, 29 March)
• Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Wednesday, 29 March)
• Re: [w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120) (Wednesday, 29 March)
• Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) (Wednesday, 29 March)
• [w3c/browser-payment-api] should .show() be user gated? (#486) (Wednesday, 29 March)
• Re: [w3c/webpayments-payment-apps-api] [Editorial] Clean up respec errors (#122) (Wednesday, 29 March)
• Re: [w3c/webpayments-payment-apps-api] Open Window Algorithm (#115) (Tuesday, 28 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Tuesday, 28 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Tuesday, 28 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Tuesday, 28 March)
• [w3c/webpayments-payment-apps-api] PaymentRequestEvent incompatible with DOM events (#119) (Tuesday, 28 March)
• Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Recipient and payerName are lacking i18n support (#471) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Clarify wording to not imply 'pull' only payments (#474) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Unclear what happens when multiple PRs call show() (#462) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Unclear what happens when multiple PRs call show() (#462) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Unclear what happens when multiple PRs call show() (#462) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Should the user agent generate the `id` when it's empty? (#483) (Tuesday, 28 March)
• Re: [w3c/webpayments-payment-apps-api] Small fixes (#114) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] `appRequest` attribute should not be a dictionary (#111) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] `appRequest` attribute should not be a dictionary (#111) (Tuesday, 21 March)
• Re: [w3c/browser-payment-api] Editorial changes (#465) (Tuesday, 21 March)
• Re: [w3c/browser-payment-api] Editorial changes (#465) (Tuesday, 21 March)
• Re: [w3c/browser-payment-api] Editorial changes (#465) (Tuesday, 21 March)
• Re: [w3c/browser-payment-api] fix: make supportedMethod conforming (#463) (Tuesday, 21 March)
• Re: [w3c/browser-payment-api] fix: make supportedMethod conforming (#463) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] `appRequest` attribute should not be a dictionary (#111) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] `appRequest` attribute should not be a dictionary (#111) (Monday, 20 March)
• Re: [w3c/webpayments-payment-apps-api] `appRequest` attribute should not be a dictionary (#111) (Monday, 20 March)
• Re: [w3c/webpayments-payment-apps-api] `appRequest` attribute should not be a dictionary (#111) (Monday, 20 March)
• Re: [w3c/webpayments-payment-apps-api] Small fixes (#114) (Monday, 20 March)
• Re: [w3c/browser-payment-api] supportedMethods (URL and enums) (#464) (Monday, 20 March)
• Re: [w3c/browser-payment-api] Editorial changes (#465) (Monday, 20 March)
• Re: [w3c/browser-payment-api] Editorial changes (#465) (Monday, 20 March)
• Re: [w3c/browser-payment-api] supportedMethods (URL and enums) (#464) (Monday, 20 March)
• Re: [w3c/browser-payment-api] supportedMethods (URL and enums) (#464) (Monday, 20 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Monday, 20 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Monday, 20 March)
• Re: [w3c/webpayments-payment-apps-api] `appRequest` attribute should not be a dictionary (#111) (Monday, 20 March)
• Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23) (Monday, 20 March)
• Re: [w3c/webpayments-method-identifiers] chore: tidy (#25) (Monday, 20 March)
• Re: [w3c/browser-payment-api] supportedMethods (URL and enums) (#464) (Monday, 20 March)
• Re: [w3c/browser-payment-api] supportedMethods (URL and enums) (#464) (Monday, 20 March)
• [w3c/browser-payment-api] supportedMethods (URL and enums) (#464) (Monday, 20 March)
• [w3c/webpayments-method-identifiers] chore: tidy (#25) (Monday, 20 March)
• [w3c/webpayments-method-identifiers] Add marcosscaceres as collaborator (#24) (Monday, 20 March)
• Re: [w3c/webpayments-method-identifiers] Why are payment ids restricted to [a-z0-9]? (#20) (Monday, 20 March)
• [w3c/browser-payment-api] fix: make supportedMethod conforming (#463) (Monday, 20 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Friday, 17 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Friday, 17 March)
• [w3c/browser-payment-api] Unclear what happens when multiple PRs are created (#462) (Friday, 17 March)
• [w3c/browser-payment-api] show() method lacks developer guidance (#461) (Friday, 17 March)
• Re: [w3c/browser-payment-api] PaymentRequest type checks (valid non-negative monetary value) (#306) (Friday, 17 March)
• Re: [w3c/browser-payment-api] PaymentRequest type checks (valid non-negative monetary value) (#306) (Friday, 17 March)
• Re: [w3c/browser-payment-api] maybe add `DisplayItem` dictionary (#457) (Friday, 17 March)
• Re: [w3c/browser-payment-api] maybe add `DisplayItem` dictionary (#457) (Friday, 17 March)
• Re: [w3c/browser-payment-api] valid decimal monetary value maybe overly restrictive (#304) (Friday, 17 March)
• Re: [w3c/browser-payment-api] Ambiguity in "Process payment methods:" (#458) (Friday, 17 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Friday, 17 March)
• Re: [w3c/webpayments-payment-apps-api] Structural changes based on task force discussion (#107) (Friday, 17 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Friday, 17 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Friday, 17 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Thursday, 16 March)
• Re: [w3c/browser-payment-api] Ambiguity in "Process payment methods:" (#458) (Thursday, 16 March)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Thursday, 16 March)
• Re: [w3c/browser-payment-api] Badness in constructor... (#459) (Thursday, 16 March)
• Re: [w3c/browser-payment-api] editorial(constructor): remove redundant line (closes #459) (#460) (Thursday, 16 March)
• Re: [w3c/browser-payment-api] editorial(constructor): remove redundant line (closes #459) (#460) (Thursday, 16 March)
• [w3c/browser-payment-api] editorial(constructor): remove redundant line (closes #459) (#460) (Thursday, 16 March)
• [w3c/browser-payment-api] Badness in constructor... (#459) (Thursday, 16 March)
• [w3c/browser-payment-api] Ambiguity in "Process payment methods:" (#458) (Thursday, 16 March)
• Re: [w3c/browser-payment-api] valid decimal monetary value maybe overly restrictive (#304) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] valid decimal monetary value maybe overly restrictive (#304) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] What does it mean to "accept the payment"? (#278) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] Need to define the interaction of payment API with navigation and browsing context destruction (#360) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] Fix constructor handling of shippingType (#452) (Wednesday, 15 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Wednesday, 15 March)
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) (Wednesday, 15 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Wednesday, 15 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Wednesday, 15 March)
• Re: [w3c/webpayments-payment-apps-api] Structural changes based on task force discussion (#107) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] maybe add `DisplayItem` dictionary (#457) (Wednesday, 15 March)
• [w3c/browser-payment-api] maybe add `DisplayItem` dictionary (#457) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] PaymentRequest type checks (valid non-negative monetary value) (#306) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] PaymentRequest type checks (valid non-negative monetary value) (#306) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] Initial values for internal slots (#436) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Tuesday, 14 March)
• [w3c/browser-payment-api] Move examples to top of document (#456) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Tuesday, 14 March)
• [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] Remove trailing comma from IDL enums (#453) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Remove trailing comma from IDL enums (#453) (Friday, 10 March)
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) (Thursday, 9 March)
• Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) (Thursday, 9 March)
• Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) (Thursday, 9 March)
• Re: [w3c/browser-payment-api] Fix constructor handling of shippingType (#452) (Thursday, 9 March)
• Re: [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Thursday, 9 March)
• Re: [w3c/browser-payment-api] Fix constructor handling of shippingType (#452) (Thursday, 9 March)
• Re: [w3c/browser-payment-api] Supporting push payment methods (#224) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] Supporting push payment methods (#224) (Wednesday, 8 March)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Wednesday, 8 March)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Wednesday, 8 March)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Wednesday, 8 March)
• Re: [w3c/webpayments-payment-apps-api] Add explicit permission call to allow payment app to handle payments (#94) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] Specify how to abort a payment request (#449) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] Section for A11Y Considerations (#450) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] Introductory explanations of methods should be non-normative notes (#379) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] PaymentResponse attributes should be separate sections (#442) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] Fix markup errors that broke autopublishing (#444) (Tuesday, 7 March)
• Re: [w3c/browser-payment-api] Fix markup errors that broke autopublishing (#444) (Tuesday, 7 March)
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Monday, 6 March)
• Re: [w3c/browser-payment-api] Make updateWith() return a promise signaling any update failures (#418) (Monday, 6 March)
• Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Monday, 6 March)
• Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Monday, 6 March)
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Monday, 6 March)
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Monday, 6 March)
• Re: [w3c/browser-payment-api] editorial: attr/method intros are notes (closes #379) (#438) (Monday, 6 March)
• Re: [w3c/browser-payment-api] PaymentRequestID initialization (#412) (Monday, 6 March)
• Re: [w3c/browser-payment-api] PaymentRequestID initialization (#412) (Monday, 6 March)
• Re: [w3c/browser-payment-api] It is never stated how the payment request ID is used (#415) (Monday, 6 March)
• Re: [w3c/browser-payment-api] Providing/Generating paymentRequestID during construction (#388) (Monday, 6 March)
• Re: [w3c/browser-payment-api] It is never stated how the payment request ID is used (#415) (Monday, 6 March)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Monday, 6 March)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Monday, 6 March)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Monday, 6 March)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Monday, 6 March)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Monday, 6 March)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Monday, 6 March)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Monday, 6 March)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Monday, 6 March)
• Re: [w3c/browser-payment-api] feat: put request id in details dictionary (#426) (Monday, 6 March)
• Re: [w3c/browser-payment-api] Why does PaymentRequest constructor throw on details.error (#302) (Monday, 6 March)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Monday, 6 March)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Monday, 6 March)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Monday, 6 March)
• Re: [w3c/browser-payment-api] Specify how to abort a payment request (#449) (Monday, 6 March)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Monday, 6 March)
• Re: [w3c/browser-payment-api] NotSupportedError in private browsing mode (#448) (Monday, 6 March)
• Re: [w3c/browser-payment-api] API assumes Issuer communication is OOB (#447) (Friday, 3 March)
• Re: [w3c/browser-payment-api] API assumes Issuer communication is OOB (#447) (Friday, 3 March)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] editorial: s/fields/members + xref fixes (closes #424) (#443) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] editorial: s/fields/members + xref fixes (closes #424) (#443) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] `PaymentInstrument.complete(result)` wording (#402) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] fix: s/user interaction/transaction (closes #402) (#432) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] editorial: s/fields/members + xref fixes (closes #424) (#443) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] fix: s/user interaction/transaction (closes #402) (#432) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] Spec talks about dictionary fields instead of dictionary members (#424) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] editorial: s/shown/presented (closes #428) (#435) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] "Shown" should be "presented" in prose (#428) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] editorial: s/fields/members + xref fixes (closes #424) (#443) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] Fix markup errors that broke autopublishing (#444) (Wednesday, 1 March)
• Re: [w3c/browser-payment-api] Fix markup errors that broke autopublishing (#444) (Wednesday, 1 March)
• Re: [w3c/browser-payment-api] Create pr-preview config file. (#445) (Wednesday, 1 March)
• Re: [w3c/browser-payment-api] Create pr-preview config file. (#445) (Wednesday, 1 March)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Wednesday, 1 March)
• Re: [w3c/browser-payment-api] Create pr-preview config file. (#445) (Wednesday, 1 March)
• Re: [w3c/browser-payment-api] Create pr-preview config file. (#445) (Wednesday, 1 March)
• Re: [w3c/browser-payment-api] Fix markup errors that broke autopublishing (#444) (Wednesday, 1 March)
• Re: [w3c/browser-payment-api] Fix markup errors that broke autopublishing (#444) (Wednesday, 1 March)
• Re: [w3c/browser-payment-api] fix: delegate total and error member checks to WebIDL (#425) (Wednesday, 1 March)

Matt N.

• Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Wednesday, 29 March)
• Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Wednesday, 29 March)

mattsaxon

• Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) (Wednesday, 29 March)
• Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Wednesday, 29 March)
• Re: [w3c/webpayments-payment-apps-api] Support for Abort() being delegated to Payment Handler (#117) (Friday, 24 March)
• Re: [w3c/browser-payment-api] Aborting of in progress push payments (#473) (Friday, 24 March)
• [w3c/webpayments-payment-apps-api] Support for Abort() being delegated to Payment Handler (#117) (Friday, 24 March)
• [w3c/browser-payment-api] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Friday, 24 March)
• [w3c/browser-payment-api] Clarity required in section 21.2 regarding (#475) (Friday, 24 March)
• [w3c/browser-payment-api] Clarify wording to not imply 'pull' only payhments (#474) (Friday, 24 March)
• Re: [w3c/browser-payment-api] Aborting of in progress push payments (#473) (Friday, 24 March)
• Re: [w3c/webpayments-methods-card] Leave Off Unneeded Information (#5) (Friday, 24 March)
• Re: [w3c/webpayments-methods-card] PaymentResponse missing filters (#28) (Thursday, 23 March)
• Re: [w3c/webpayments-methods-card] PaymentResponse missing filters (#28) (Thursday, 23 March)
• [w3c/webpayments-methods-card] PymentResponse missing filters (#28) (Thursday, 23 March)
• [w3c/browser-payment-api] Aborting of in progress push payments (#473) (Thursday, 23 March)
• [w3c/browser-payment-api] 'Interactive' Bias in API (#467) (Wednesday, 22 March)
• [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) (Wednesday, 22 March)

Michael[tm] Smith

• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] Fix markup errors that broke autopublishing (#444) (Tuesday, 7 March)
• Re: [w3c/browser-payment-api] Fix markup errors that broke autopublishing (#444) (Wednesday, 1 March)
• Re: [w3c/browser-payment-api] Create pr-preview config file. (#445) (Wednesday, 1 March)
• Re: [w3c/browser-payment-api] Create pr-preview config file. (#445) (Wednesday, 1 March)
• Re: [w3c/browser-payment-api] Create pr-preview config file. (#445) (Wednesday, 1 March)

Michel Weksler

• Re: [w3c/browser-payment-api] Consider removing merchant preference language (#481) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Consider removing merchant preference language (#481) (Friday, 24 March)

Nick Shearer

• Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Wednesday, 29 March)
• [w3c/browser-payment-api] Supplement QuoteExceededError with NotAllowedError for canMakePayments (#485) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Consider removing merchant preference language (#481) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Recipient and payerName are lacking i18n support (#471) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Recipient and payerName are lacking i18n support (#471) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Tuesday, 28 March)
• [w3c/browser-payment-api] Recipient and payerName are lacking i18n support (#471) (Thursday, 23 March)
• Re: [w3c/browser-payment-api] 'Interactive' Bias in API (#467) (Thursday, 23 March)

PASCAL J. BAZIN

• Re: [w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109) (Thursday, 16 March)

Per Thomas Jahr

• Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Friday, 31 March)
• Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Thursday, 30 March)
• [w3c/browser-payment-api] Should user agent validate currency? (#490) (Thursday, 30 March)

r12a

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

Rouslan Solomakhin

• Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Friday, 31 March)
• Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Friday, 31 March)
• Re: [w3c/webpayments-payment-apps-api] Should `modifiers` be passed to the payment handler? (#118) (Wednesday, 29 March)
• Re: [w3c/webpayments-payment-apps-api] Should `modifiers` be passed to the payment handler? (#118) (Wednesday, 29 March)
• Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) (Wednesday, 29 March)
• Re: [w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120) (Wednesday, 29 March)
• Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Wednesday, 29 March)
• Re: [w3c/browser-payment-api] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Supplement QuoteExceededError with NotAllowedError for canMakePayments (#485) (Tuesday, 28 March)
• Re: [w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120) (Tuesday, 28 March)
• [w3c/browser-payment-api] Should the user agent generate the `id` when it's empty? (#483) (Monday, 27 March)
• Re: [w3c/webpayments-payment-apps-api] Should `modifiers` be passed to the payment handler? (#118) (Monday, 27 March)
• [w3c/webpayments-payment-apps-api] Should `modifiers` be passed to the payment handler? (#118) (Monday, 27 March)
• Re: [w3c/browser-payment-api] Unclear what happens when multiple PRs call show() (#462) (Saturday, 25 March)
• Re: [w3c/webpayments-payment-apps-api] Support for Abort() being delegated to Payment Handler (#117) (Friday, 24 March)
• Re: [w3c/browser-payment-api] Unclear what happens when multiple PRs call show() (#462) (Friday, 24 March)
• Re: [w3c/browser-payment-api] Unclear what happens when multiple PRs call show() (#462) (Thursday, 23 March)
• Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) (Wednesday, 22 March)
• [w3c/webpayments-payment-apps-api] `appRequest` attribute should not be a dictionary (#111) (Friday, 17 March)
• Re: [w3c/browser-payment-api] Ambiguity in "Process payment methods:" (#458) (Thursday, 16 March)
• Re: [w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109) (Thursday, 16 March)
• Re: [w3c/browser-payment-api] valid decimal monetary value maybe overly restrictive (#304) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] valid decimal monetary value maybe overly restrictive (#304) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Fix constructor handling of shippingType (#452) (Thursday, 9 March)
• Re: [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Thursday, 9 March)
• Re: [w3c/browser-payment-api] Specify how to abort a payment request (#449) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] NotSupportedError in private browsing mode (#448) (Monday, 6 March)
• [w3c/browser-payment-api] NotSupportedError in private browsing mode (#448) (Monday, 6 March)

Shane McCarron

• Re: [w3c/browser-payment-api] Section for A11Y Considerations (#450) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] Section for A11Y Considerations (#450) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] Section for A11Y Considerations (#450) (Wednesday, 8 March)
• Re: [w3c/browser-payment-api] Section for A11Y Considerations (#450) (Wednesday, 8 March)
• [w3c/browser-payment-api] Section for A11Y Considerations (#450) (Tuesday, 7 March)

Simon Pieters

• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Wednesday, 15 March)
• [w3c/browser-payment-api] Remove trailing comma from IDL enums (#453) (Friday, 10 March)

stan-stripe

• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Thursday, 2 March)

Tobie Langel

• Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Tuesday, 14 March)
• Re: [w3c/browser-payment-api] editorial: s/fields/members + xref fixes (closes #424) (#443) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] Create pr-preview config file. (#445) (Wednesday, 1 March)

Tommy Thorsen

• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Tuesday, 21 March)
• [w3c/webpayments-payment-apps-api] Open Window Algorithm (#115) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Tuesday, 21 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Monday, 20 March)
• Re: [w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109) (Monday, 20 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Friday, 17 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Friday, 17 March)
• Re: [w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109) (Thursday, 16 March)
• [w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109) (Thursday, 16 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Thursday, 16 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Wednesday, 15 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Wednesday, 15 March)
• [w3c/webpayments-payment-apps-api] Run the spec through HTML5-Tidy. (#108) (Wednesday, 15 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Wednesday, 15 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Wednesday, 15 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Wednesday, 15 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Wednesday, 15 March)
• Re: [w3c/webpayments-payment-apps-api] Different approaches to opening windows (#97) (Wednesday, 15 March)
• Re: [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Wednesday, 15 March)
• [w3c/webpayments-payment-apps-api] Change from clients.openWindow to event.openWindow. (#106) (Tuesday, 14 March)
• Re: [w3c/webpayments-payment-apps-api] Proposed changes for #95 (and #96) (#104) (Tuesday, 7 March)
• Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Wednesday, 1 March)

Zach Koch

• Re: [w3c/browser-payment-api] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Wednesday, 29 March)
• Re: [w3c/browser-payment-api] Behavior for multiple modifiers for the same payment method is not defined (#309) (Wednesday, 29 March)
• Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Wednesday, 29 March)
• Re: [w3c/browser-payment-api] Consider removing merchant preference language (#481) (Tuesday, 28 March)
• Re: [w3c/browser-payment-api] Supplement QuoteExceededError with NotAllowedError for canMakePayments (#485) (Tuesday, 28 March)
• [w3c/browser-payment-api] Consider removing merchant preference language (#481) (Friday, 24 March)
• [w3c/browser-payment-api] Editors to figure out text on line items (#477) (Friday, 24 March)
• Re: [w3c/webpayments-methods-card] PaymentResponse missing filters (#28) (Thursday, 23 March)
• Re: [w3c/browser-payment-api] fix(complete): bugus result value will have thrown already (#468) (Thursday, 23 March)
• Re: [w3c/browser-payment-api] fix(complete): bugus result value will have thrown already (#468) (Thursday, 23 March)
• [w3c/browser-payment-api] Add explicit extension point to matching algo (#470) (Thursday, 23 March)
• Re: [w3c/browser-payment-api] 'Interactive' Bias in API (#467) (Thursday, 23 March)
• Re: [w3c/browser-payment-api] supportedMethods (URL and enums) (#464) (Thursday, 23 March)
• Re: [w3c/browser-payment-api] Unclear what happens when multiple PRs call show() (#462) (Wednesday, 22 March)
• Re: [w3c/browser-payment-api] updateWith will silently ignore data in hard-to-debug ways (#350) (Wednesday, 22 March)
• Re: [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Wednesday, 22 March)
• Re: [w3c/browser-payment-api] Make updateWith() reject the show() promise on validation failures (#451) (Wednesday, 22 March)
• Re: [w3c/browser-payment-api] Addition of flag on PaymentMethodData to indicate that line items should be shared with apps (#446) (Thursday, 16 March)
• Re: [w3c/browser-payment-api] Addition of flag on PaymentMethodData to indicate that line items should be shared with apps (#446) (Thursday, 16 March)
• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] How can a user agent not accept a payment method? (#273) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] How can a user agent not accept a payment method? (#273) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] What does it mean to "accept the payment"? (#278) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] Should values for supportedNetworks be defined in Basic Card or separately? (#325) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] Should values for supportedNetworks be defined in Basic Card or separately? (#325) (Wednesday, 15 March)
• Re: [w3c/webpayments-methods-card] Add link to list of card networks (#25) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] Define payment option filtering algorithm. (#420) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] Define payment option filtering algorithm. (#420) (Wednesday, 15 March)
• Re: [w3c/browser-payment-api] PaymentRequest type checks (valid non-negative monetary value) (#306) (Monday, 13 March)
• Re: [w3c/browser-payment-api] PaymentRequest does not handle the case of store pickup (#389) (Monday, 13 March)
• Re: [w3c/browser-payment-api] PaymentApp fails to abort payment flow (#384) (Monday, 13 March)
• Re: [w3c/browser-payment-api] PaymentApp fails to abort payment flow (#384) (Monday, 13 March)
• Re: [w3c/browser-payment-api] Should values for supportedNetworks be defined in Basic Card or separately? (#325) (Monday, 13 March)
• Re: [w3c/browser-payment-api] Initial values for internal slots (#436) (Monday, 13 March)
• Re: [w3c/browser-payment-api] Fix constructor handling of shippingType (#452) (Friday, 10 March)
• Re: [w3c/browser-payment-api] Fix constructor handling of shippingType (#452) (Thursday, 9 March)
• Re: [w3c/browser-payment-api] fix: s/user interaction/transaction (closes #402) (#432) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] PaymentApp fails to abort payment flow (#384) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] PaymentRequest does not handle the case of store pickup (#389) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] Add billing shipping type (#409) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] fix: s/user interaction/transaction (closes #402) (#432) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] editorial: s/shown/presented (closes #428) (#435) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] editorial: s/fields/members + xref fixes (closes #424) (#443) (Thursday, 2 March)
• Re: [w3c/browser-payment-api] editorial: s/fields/members + xref fixes (closes #424) (#443) (Thursday, 2 March)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Wednesday, 1 March)
• Re: [w3c/webpayments-payment-apps-api] Why does a Payment App need to see the line items? (#91) (Wednesday, 1 March)

Last message date: Friday, 31 March 2017 18:12:33 UTC