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

adamroach

Re: [w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121) (Monday, 3 April)

Ade Bateman

Re: [w3c/browser-payment-api] Remove 2119 language from privacy section. (#511) (Thursday, 27 April)
[w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512) (Thursday, 27 April)
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Thursday, 27 April)
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Wednesday, 26 April)
Re: [w3c/browser-payment-api] 'Interactive' Bias in API (#467) (Wednesday, 26 April)
[w3c/browser-payment-api] Remove 2119 language from privacy section. (#511) (Wednesday, 26 April)
Re: [w3c/webpayments-method-identifiers] If URL parsing fails then always fail to match URLs. (#31) (Thursday, 20 April)
[w3c/webpayments-method-identifiers] If URL parsing fails then always fail to match URLs. (#31) (Thursday, 20 April)
Re: [w3c/webpayments-method-identifiers] Circular dependency between PMI and PR specs (#22) (Wednesday, 19 April)
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Wednesday, 12 April)

Adrian Hope-Bailie

Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] If URL parsing fails then always fail to match URLs. (#31) (Thursday, 20 April)
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Thursday, 20 April)
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Thursday, 20 April)
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Thursday, 20 April)
Re: [w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127) (Wednesday, 19 April)
Re: [w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127) (Wednesday, 19 April)
[w3c/webpayments-payment-handler] Merge PaymentAppResponse and PaymentRequestEvent (#142) (Wednesday, 19 April)
Re: [w3c/webpayments-payment-handler] respec fix (#141) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Improve payment app arch image (#140) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Define event handler before payment manager (#134) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Improve payment app arch image (#140) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Tuesday, 18 April)
[w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Monday, 17 April)
Re: [w3c/webpayments-payment-handler] Tidy (#137) (Monday, 17 April)
Re: [w3c/webpayments-payment-handler] Tidy (#137) (Monday, 17 April)
Re: [w3c/webpayments-payment-handler] Updated short name and URL for new repo name (#136) (Monday, 17 April)
[w3c/webpayments-payment-handler] Update README.md to link to new repo (#135) (Monday, 17 April)
Re: [w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) (Saturday, 15 April)
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) (Saturday, 15 April)
Re: [w3c/webpayments-payment-apps-api] Define event handler before payment manager (#134) (Saturday, 15 April)
Re: [w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) (Friday, 14 April)
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) (Friday, 14 April)
[w3c/webpayments-payment-apps-api] Define event handler before payment manager (#134) (Friday, 14 April)
Re: [w3c/webpayments-payment-apps-api] Do we need "Payment Manager" and "Payment Handler"? (#127) (Friday, 14 April)
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Wednesday, 12 April)
Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) (Wednesday, 5 April)
Re: [w3c/browser-payment-api] Consider adding examples of payment matching algorithm (#498) (Wednesday, 5 April)
Re: [w3c/webpayments-payment-apps-api] Support for Abort() being delegated to Payment Handler (#117) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Add extension point (#492) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Monday, 3 April)
Re: [w3c/browser-payment-api] Add extension point (#492) (Monday, 3 April)
Re: [w3c/browser-payment-api] Add extension point (#492) (Monday, 3 April)
Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) (Monday, 3 April)
Re: [w3c/webpayments-payment-apps-api] Share user data with Payment App (#123) (Monday, 3 April)
Re: [w3c/browser-payment-api] Add explicit extension point to matching algo (#470) (Monday, 3 April)
Re: [w3c/browser-payment-api] Add postMessage() and addMessageListener() for enabling "in-bound" communication (#494) (Monday, 3 April)
Re: [w3c/webpayments-methods-card] Leave Off Unneeded Information (#5) (Sunday, 2 April)
[w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) (Saturday, 1 April)
Re: [w3c/browser-payment-api] maybe add `DisplayItem` dictionary (#457) (Saturday, 1 April)
Re: [w3c/webpayments-payment-apps-api] Share user data with Payment App (#123) (Saturday, 1 April)
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Saturday, 1 April)
Re: [w3c/webpayments-methods-card] Leave Off Unneeded Information (#5) (Saturday, 1 April)
[w3c/browser-payment-api] Add extension point (#492) (Saturday, 1 April)

Anders Rundgren

Anne van Kesteren

Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] If URL parsing fails then always fail to match URLs. (#31) (Thursday, 27 April)

Daniel Lewis

Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) (Tuesday, 25 April)

Dave Longley

Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Tuesday, 18 April)
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Thursday, 6 April)
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Thursday, 6 April)

Domenic Denicola

Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512) (Thursday, 27 April)
Re: [w3c/browser-payment-api] editorial: s/target/request in updateWith() algo (#517) (Thursday, 27 April)
Re: [w3c/browser-payment-api] editorial: use DOM relatedTarget instead of .target (closes #513) (#515) (Thursday, 27 April)
Re: [w3c/browser-payment-api] editorial: xref EventInit in DOM spec (#514) (Thursday, 27 April)
Re: [w3c/browser-payment-api] Remove 2119 language from privacy section. (#511) (Thursday, 27 April)
Re: [w3c/browser-payment-api] Define expected behavior when no 'shippingaddresschange ' event listener is defined (#507) (Wednesday, 26 April)
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) (Wednesday, 26 April)
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) (Monday, 24 April)
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) (Monday, 24 April)
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) (Monday, 24 April)
Re: [w3c/browser-payment-api] Define expected behavior when no 'shippingaddresschange ' event listener is defined (#507) (Monday, 24 April)
Re: [w3c/browser-payment-api] l10n: adds Localizable dict + TextDirection enum (closes #327) (#455) (Monday, 24 April)
Re: [w3c/browser-payment-api] Define expected behavior when no 'shippingaddresschange ' event listener is defined (#507) (Monday, 24 April)
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) (Monday, 10 April)
[w3c/browser-payment-api] Editorial: paymentResponse.complete() should return a rejected promise, not throw (#509) (Monday, 10 April)
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) (Monday, 10 April)
Re: [w3c/browser-payment-api] fix: broken links to HTML (closes #502) (#504) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] PaymentAddress and null values (#495) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] PaymentAddress and null values (#495) (Tuesday, 4 April)

Edouard Chin

Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) (Thursday, 27 April)
Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) (Thursday, 27 April)
Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) (Wednesday, 26 April)
Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) (Wednesday, 26 April)

frank-hoffmann

Re: [w3c/webpayments-payment-apps-api] Add support for topLevelOrigin and paymentRequestOrigin (#130) (Thursday, 13 April)

ianbjacobs

[w3c/browser-payment-api] Redo PR 506 (on merchant prefs) (#518) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) (Friday, 28 April)
Re: [w3c/browser-payment-api] Editorial: consider removing merchant preference language (#506) (Thursday, 27 April)
Re: [w3c/browser-payment-api] Editorial: consider removing merchant preference language (#506) (Thursday, 27 April)
Re: [w3c/browser-payment-api] Editorial: consider removing merchant preference language (#506) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] [SECURE-CONTEXTS] should be a normative rather than informative reference (#29) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] [SECURE-CONTEXTS] should be a normative rather than informative reference (#29) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Remove "Conditional Matching Beyond Payment Method Identifier Matching" (#34) (Thursday, 27 April)
Re: [w3c/browser-payment-api] Remove 2119 language from privacy section. (#511) (Thursday, 27 April)
Re: [w3c/webpayments-payment-handler] Merge PaymentAppResponse and PaymentRequestEvent (#142) (Friday, 21 April)
Re: [w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#18) (Thursday, 20 April)
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Thursday, 20 April)
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Thursday, 20 April)
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Thursday, 20 April)
Re: [w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#18) (Thursday, 20 April)
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Wednesday, 19 April)
Re: [w3c/webpayments-methods-card] Clarify this specification is intended to become a W3C Note (#27) (Wednesday, 19 April)
Re: [w3c/webpayments-payment-handler] respec fix (#141) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] respec fix (#141) (Tuesday, 18 April)
[w3c/webpayments-payment-handler] respec fix (#141) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Improve payment app arch image (#140) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Improve payment app arch image (#140) (Tuesday, 18 April)
[w3c/webpayments-payment-handler] Improve payment app arch image (#140) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Passing modifiers to payment apps (#139) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Monday, 17 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Monday, 17 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Monday, 17 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Monday, 17 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Monday, 17 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Monday, 17 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Monday, 17 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Monday, 17 April)
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) (Monday, 17 April)
Re: [w3c/webpayments-payment-handler] Tidy (#137) (Monday, 17 April)
[w3c/webpayments-payment-handler] Tidy (#137) (Monday, 17 April)
Re: [w3c/webpayments-payment-handler] Update README.md to link to new repo (#135) (Monday, 17 April)
Re: [w3c/webpayments-payment-handler] Updated short name and URL for new repo name (#136) (Monday, 17 April)
Re: [w3c/webpayments-payment-handler] Update README.md to link to new repo (#135) (Monday, 17 April)
[w3c/webpayments-payment-handler] Updated short name and URL for new repo name (#136) (Monday, 17 April)
Re: [w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) (Saturday, 15 April)
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) (Saturday, 15 April)
Re: [w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) (Saturday, 15 April)
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) (Saturday, 15 April)
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) (Friday, 14 April)
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) (Friday, 14 April)
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) (Friday, 14 April)
Re: [w3c/webpayments-payment-apps-api] Define event handler before payment manager (#134) (Friday, 14 April)
Re: [w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) (Friday, 14 April)
[w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Pictures would help! (#49) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) (Thursday, 13 April)
[w3c/webpayments-payment-apps-api] Diagrams (#132) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] WebIDL fix (#131) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Add support for topLevelOrigin and paymentRequestOrigin (#130) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Add support for topLevelOrigin and paymentRequestOrigin (#130) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Add support for topLevelOrigin and paymentRequestOrigin (#130) (Thursday, 13 April)
[w3c/webpayments-payment-apps-api] WebIDL fix (#131) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120) (Thursday, 13 April)
[w3c/webpayments-payment-apps-api] Add support for topLevelOrigin and paymentRequestOrigin (#130) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Add .clear() to map-likes (#129) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] [Editorial] Clean up respec errors (#122) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] [Editorial] Clean up respec errors (#122) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Wednesday, 12 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Wednesday, 12 April)
[w3c/webpayments-payment-apps-api] Revisit Examples 3 and 4 (#128) (Wednesday, 12 April)
[w3c/webpayments-payment-apps-api] Do we need "Payment Manager" and "Payment Handler"? (#127) (Wednesday, 12 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Wednesday, 12 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Wednesday, 12 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Wednesday, 12 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Wednesday, 12 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Wednesday, 12 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Wednesday, 12 April)
Re: [w3c/webpayments-method-identifiers] citation to dated version of since-abandoned url spec fork is unusual (#30) (Tuesday, 11 April)
Re: [w3c/browser-payment-api] Edits for issue 481 (#506) (Tuesday, 11 April)
Re: [w3c/browser-payment-api] Edits for issue 481 (#506) (Tuesday, 11 April)
Re: [w3c/browser-payment-api] Edits for issue 481 (#506) (Tuesday, 11 April)
Re: [w3c/browser-payment-api] Edits for issue 481 (#506) (Tuesday, 11 April)
Re: [w3c/browser-payment-api] Edits for issue 481 (#506) (Friday, 7 April)
[w3c/browser-payment-api] Edits for issue 481 (#506) (Friday, 7 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Thursday, 6 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Thursday, 6 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Thursday, 6 April)
Re: [w3c/webpayments-payment-apps-api] Respect fixes (#126) (Wednesday, 5 April)
[w3c/webpayments-payment-apps-api] Respect fixes (#126) (Wednesday, 5 April)
Re: [w3c/browser-payment-api] Consider removing merchant preference language (#481) (Wednesday, 5 April)
Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) (Wednesday, 5 April)
Re: [w3c/webpayments-payment-apps-api] [Privacy] Clarify what information user agents forget at various moments (#124) (Wednesday, 5 April)
Re: [w3c/webpayments-payment-apps-api] [Privacy] Clarify what information user agents forget at various moments (#124) (Wednesday, 5 April)
Re: [w3c/browser-payment-api] Editors to figure out text on line items (#477) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] Relation between merchant order of payment methods and payment app order of instruments (#116) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] Pictures would help! (#49) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] Recommended payment apps (#74) (Tuesday, 4 April)
[w3c/webpayments-payment-apps-api] Image object is undefined (#125) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] What does "icon" mean? (#69) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] What does "icon" mean? (#69) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] [Privacy] Clarify what information user agents forget at various moments (#124) (Tuesday, 4 April)
[w3c/browser-payment-api] Missing (normative) reference to BPC-47 (language code) (#503) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] Display may be subject to user and local policy (consider UA making security decisions etc) (#5) (Monday, 3 April)
Re: [w3c/browser-payment-api] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Monday, 3 April)
Re: [w3c/browser-payment-api] Payment App or Payment Handler language (#497) (Monday, 3 April)
Re: [w3c/browser-payment-api] Reference to payment apps in Introduction needs updating (#496) (Monday, 3 April)
Re: [w3c/browser-payment-api] 'Pull' Payment Bias in API spec (#499) (Monday, 3 April)
Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) (Monday, 3 April)
[w3c/webpayments-methods-card] Add an excludedFields BasicCardRequest parameter (#29) (Monday, 3 April)
Re: [w3c/browser-payment-api] Add extension point (#492) (Monday, 3 April)
Re: [w3c/browser-payment-api] Add extension point (#492) (Monday, 3 April)
Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) (Monday, 3 April)
Re: [w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121) (Monday, 3 April)
Re: [w3c/browser-payment-api] Clarify use of API in (or not in) Secure Contexts (#501) (Monday, 3 April)
Re: [w3c/browser-payment-api] Clarify use of API in (or not in) Secure Contexts (#501) (Monday, 3 April)
[w3c/webpayments-payment-apps-api] [Privacy] Clarify what information user agents forget at various moments (#124) (Monday, 3 April)
[w3c/browser-payment-api] Clarify use of API in (or not in) Secure Contexts (#501) (Monday, 3 April)
Re: [w3c/webpayments-methods-card] Leave Off Unneeded Information (#5) (Sunday, 2 April)
Re: [w3c/browser-payment-api] Add postMessage() and addMessageListener() for enabling "in-bound" communication (#494) (Sunday, 2 April)
Re: [w3c/browser-payment-api] Add postMessage() and addMessageListener() for enabling "in-bound" communication (#494) (Sunday, 2 April)

Jeff Burdges

Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) (Wednesday, 26 April)
Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) (Wednesday, 26 April)

Jinho Bang

KJM

Re: [w3c/webpayments-payment-apps-api] Relation between merchant order of payment methods and payment app order of instruments (#116) (Thursday, 6 April)

L. David Baron

[w3c/webpayments-method-identifiers] citation to dated version of since-abandoned url spec fork is unusual (#30) (Tuesday, 11 April)
[w3c/webpayments-method-identifiers] [SECURE-CONTEXTS] should be a normative rather than informative reference (#29) (Tuesday, 11 April)
Re: [w3c/webpayments-method-identifiers] [SECURE-CONTEXTS] should be a normative rather than informative reference (#29) (Tuesday, 11 April)
[w3c/webpayments-method-identifiers] use of 'must' in section on Syntax of URLs as Payment Method Identifiers is suspicious (#28) (Tuesday, 11 April)
[w3c/webpayments-methods-card] list/registry of approved card network identifiers should be listed in references section (#32) (Tuesday, 11 April)
[w3c/webpayments-methods-card] security and privacy considerations section seems insufficient (#31) (Tuesday, 11 April)
[w3c/webpayments-methods-card] No description of BasicCardResponse's billingAddress (#30) (Tuesday, 11 April)

lararennie

Re: [w3c/browser-payment-api] Provide better mapping between PaymentAddress and HTML5 autofill (#505) (Friday, 7 April)
Re: [w3c/browser-payment-api] Provide better mapping between PaymentAddress and HTML5 autofill (#505) (Friday, 7 April)

Marcos Cáceres

Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/browser-payment-api] Editorial: consider removing merchant preference language (#506) (Friday, 28 April)
Re: [w3c/browser-payment-api] Editorial: consider removing merchant preference language (#506) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) (Thursday, 27 April)
Re: [w3c/browser-payment-api] supportedMethods (URL and DOMString) (#464) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] [SECURE-CONTEXTS] should be a normative rather than informative reference (#29) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] [SECURE-CONTEXTS] should be a normative rather than informative reference (#29) (Thursday, 27 April)
Re: [w3c/browser-payment-api] Editorial: event `.target` attribute should be relatedTarget (#513) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] [SECURE-CONTEXTS] should be a normative rather than informative reference (#29) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Payment Method Identifier needs dfn (#23) (Thursday, 27 April)
[w3c/webpayments-method-identifiers] editorial: rm 'Conditional Matching Beyond Payment Methods' section (#36) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] Remove "Conditional Matching Beyond Payment Method Identifier Matching" (#34) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] If URL parsing fails then always fail to match URLs. (#31) (Thursday, 27 April)
[w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Thursday, 27 April)
[w3c/webpayments-method-identifiers] Remove "Conditional Matching Beyond Payment Method Identifier Matching" (#34) (Thursday, 27 April)
[w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) (Thursday, 27 April)
Re: [w3c/browser-payment-api] editorial: use DOM relatedTarget instead of .target (closes #513) (#515) (Thursday, 27 April)
Re: [w3c/browser-payment-api] editorial: use DOM relatedTarget instead of .target (closes #513) (#515) (Thursday, 27 April)
Re: [w3c/browser-payment-api] editorial: s/target/request in updateWith() algo (#517) (Thursday, 27 April)
Re: [w3c/browser-payment-api] editorial: xref EventInit in DOM spec (#514) (Thursday, 27 April)
Re: [w3c/browser-payment-api] Remove 2119 language from privacy section. (#511) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] If URL parsing fails then always fail to match URLs. (#31) (Thursday, 27 April)
[w3c/webpayments-method-identifiers] "W3C String" is overly generic (#32) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] SRI on manifest (#18) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] SRI on manifest (#18) (Thursday, 27 April)
Re: [w3c/webpayments-method-identifiers] [SECURE-CONTEXTS] should be a normative rather than informative reference (#29) (Thursday, 27 April)
[w3c/browser-payment-api] editorial: s/target/request in updateWith() algo (#516) (Thursday, 27 April)
Re: [w3c/browser-payment-api] Editorial: event `.target` attribute should be relatedTarget (#513) (Thursday, 27 April)
Re: [w3c/browser-payment-api] editorial: s/target/request in updateWith() algo (#516) (Thursday, 27 April)
[w3c/browser-payment-api] editorial: s/target/request in updateWith() algo (#517) (Thursday, 27 April)
Re: [w3c/browser-payment-api] editorial: s/target/request in updateWith() algo (#516) (Thursday, 27 April)
Re: [w3c/browser-payment-api] 'Interactive' Bias in API (#467) (Thursday, 27 April)
Re: [w3c/browser-payment-api] 'Interactive' Bias in API (#467) (Thursday, 27 April)
[w3c/browser-payment-api] editorial: use DOM relatedTarget instead of .target (closes #513) (#515) (Thursday, 27 April)
[w3c/browser-payment-api] editorial: xref EventInit in DOM spec (#514) (Thursday, 27 April)
[w3c/browser-payment-api] Editorial: event `.target` attribute should be relatedTarget (#513) (Thursday, 27 April)
Re: [w3c/browser-payment-api] Editorial: consider removing merchant preference language (#506) (Thursday, 27 April)
Re: [w3c/browser-payment-api] Remove 2119 language from privacy section. (#511) (Thursday, 27 April)
Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) (Wednesday, 26 April)
Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) (Wednesday, 26 April)
Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) (Wednesday, 26 April)
Re: [w3c/browser-payment-api] Missing (normative) reference to BPC-47 (language code) (#503) (Thursday, 20 April)
Re: [w3c/browser-payment-api] Added BCP ref (#510) (Thursday, 20 April)
Re: [w3c/browser-payment-api] Added BCP ref (#510) (Thursday, 20 April)
Re: [w3c/browser-payment-api] Added BCP ref (#510) (Thursday, 20 April)
Re: [w3c/browser-payment-api] Added BCP ref (#510) (Wednesday, 19 April)
Re: [w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) (Saturday, 15 April)
Re: [w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) (Saturday, 15 April)
Re: [w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) (Saturday, 15 April)
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) (Saturday, 15 April)
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) (Saturday, 15 April)
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) (Saturday, 15 April)
Re: [w3c/browser-payment-api] Define expected behavior when no 'shippingaddresschange ' event listener is defined (#507) (Saturday, 15 April)
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) (Friday, 14 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Thursday, 13 April)
[w3c/webpayments-payment-apps-api] Add .clear() to map-likes (#129) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Thursday, 13 April)
Re: [w3c/browser-payment-api] Unclear what happens when multiple PRs call show() (#462) (Wednesday, 12 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Wednesday, 12 April)
Re: [w3c/webpayments-method-identifiers] citation to dated version of since-abandoned url spec fork is unusual (#30) (Tuesday, 11 April)
Re: [w3c/browser-payment-api] Edits for issue 481 (#506) (Tuesday, 11 April)
Re: [w3c/browser-payment-api] Edits for issue 481 (#506) (Tuesday, 11 April)
Re: [w3c/browser-payment-api] Edits for issue 481 (#506) (Monday, 10 April)
Re: [w3c/browser-payment-api] Edits for issue 481 (#506) (Monday, 10 April)
Re: [w3c/browser-payment-api] Edits for issue 481 (#506) (Monday, 10 April)
Re: [w3c/browser-payment-api] Provide better mapping between PaymentAddress and HTML5 autofill (#505) (Friday, 7 April)
Re: [w3c/browser-payment-api] Provide better mapping between PaymentAddress and HTML5 autofill (#505) (Friday, 7 April)
Re: [w3c/browser-payment-api] Provide better mapping between PaymentAddress and HTML5 autofill (#505) (Friday, 7 April)
[w3c/browser-payment-api] Provide better mapping between PaymentAddress and HTML5 autofill (#505) (Friday, 7 April)
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Thursday, 6 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Thursday, 6 April)
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Thursday, 6 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Thursday, 6 April)
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) (Thursday, 6 April)
Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) (Wednesday, 5 April)
Re: [w3c/webpayments-payment-apps-api] [Privacy] Clarify what information user agents forget at various moments (#124) (Wednesday, 5 April)
Re: [w3c/webpayments-payment-apps-api] Image object is undefined (#125) (Wednesday, 5 April)
Re: [w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] [Privacy] Clarify what information user agents forget at various moments (#124) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Clarify use of API in (or not in) Secure Contexts (#501) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Clarify use of API in (or not in) Secure Contexts (#501) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Consider adding examples of payment matching algorithm (#498) (Tuesday, 4 April)
Re: [w3c/webpayments-methods-card] Add an excludedFields BasicCardRequest parameter (#29) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] fix: broken links to HTML (closes #502) (#504) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Reference to payment apps in Introduction needs updating (#496) (Tuesday, 4 April)
[w3c/browser-payment-api] fix: broken links to HTML (closes #502) (#504) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Add extension point (#492) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Adding legal entity types for consistency (#491) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Adding legal entity types for consistency (#491) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Adding legal entity types for consistency (#491) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] PaymentAddress and null values (#495) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] PaymentAddress and null values (#495) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] Clarify use of API in (or not in) Secure Contexts (#501) (Monday, 3 April)
Re: [w3c/browser-payment-api] PaymentAddress and null values (#495) (Monday, 3 April)
Re: [w3c/browser-payment-api] PaymentAddress and null values (#495) (Monday, 3 April)
Re: [w3c/browser-payment-api] PaymentAddress and null values (#495) (Monday, 3 April)
[w3c/browser-payment-api] ShippingAddress and null values (#495) (Monday, 3 April)
Re: [w3c/webpayments-payment-apps-api] Share user data with Payment App (#123) (Monday, 3 April)
Re: [w3c/browser-payment-api] maybe add `DisplayItem` dictionary (#457) (Monday, 3 April)
Re: [w3c/browser-payment-api] Add postMessage() and addMessageListener() for enabling "in-bound" communication (#494) (Monday, 3 April)
Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) (Monday, 3 April)
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Monday, 3 April)
Re: [w3c/browser-payment-api] Add extension point (#492) (Monday, 3 April)
Re: [w3c/browser-payment-api] Add extension point (#492) (Monday, 3 April)

Matt Gaunt

Matt Saxon

mattsaxon

Re: [w3c/browser-payment-api] Edits for issue 481 (#506) (Thursday, 20 April)
Re: [w3c/webpayments-methods-card] Add an excludedFields BasicCardRequest parameter (#29) (Thursday, 20 April)
Re: [w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127) (Thursday, 20 April)
Re: [w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127) (Thursday, 20 April)
Re: [w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127) (Wednesday, 19 April)
Re: [w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127) (Wednesday, 19 April)
Re: [w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127) (Wednesday, 19 April)
Re: [w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127) (Tuesday, 18 April)
Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) (Wednesday, 5 April)
Re: [w3c/webpayments-payment-apps-api] Support for Abort() being delegated to Payment Handler (#117) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Tuesday, 4 April)
Re: [w3c/webpayments-methods-card] Add an excludedFields BasicCardRequest parameter (#29) (Tuesday, 4 April)
Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) (Tuesday, 4 April)
Re: [w3c/browser-payment-api] 'Pull' Payment Bias in API spec (#499) (Tuesday, 4 April)
Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) (Monday, 3 April)
Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) (Monday, 3 April)
[w3c/browser-payment-api] State change issues in updateWith() (#500) (Monday, 3 April)
[w3c/browser-payment-api] 'Pull' Payment Bias in API spec (#499) (Monday, 3 April)
Re: [w3c/browser-payment-api] Payment App or Payment Handler language (#497) (Monday, 3 April)
[w3c/browser-payment-api] Consider adding examples of payment matching algorithm (#498) (Monday, 3 April)
[w3c/browser-payment-api] Payment App or Payment Handler language (#497) (Monday, 3 April)
[w3c/browser-payment-api] Reference to payment apps in Introduction needs updating (#496) (Monday, 3 April)
Re: [w3c/webpayments-methods-card] Leave Off Unneeded Information (#5) (Sunday, 2 April)

Molly Dalton

[w3c/browser-payment-api] Added BCP ref (#510) (Wednesday, 19 April)

Nick Doty

[w3c/browser-payment-api] Links to some HTML definitions are broken (#502) (Monday, 3 April)

Nick Shearer

Re: [w3c/browser-payment-api] Define expected behavior when no 'shippingaddresschange ' event listener is defined (#507) (Tuesday, 11 April)
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Tuesday, 11 April)

Nick Telford-Reed

Re: [w3c/browser-payment-api] Edits for issue 481 (#506) (Thursday, 20 April)

Rouslan Solomakhin

Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) (Thursday, 27 April)
Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) (Wednesday, 26 April)
Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) (Wednesday, 26 April)
Re: [w3c/webpayments-payment-handler] Passing modifiers to payment apps (#139) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-handler] Passing modifiers to payment apps (#139) (Tuesday, 18 April)
[w3c/webpayments-payment-handler] Passing modifiers to payment apps (#139) (Tuesday, 18 April)
Re: [w3c/webpayments-payment-apps-api] Do we need "Payment Manager" and "Payment Handler"? (#127) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Add support for topLevelOrigin and paymentRequestOrigin (#130) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] WebIDL fix (#131) (Thursday, 13 April)
Re: [w3c/webpayments-payment-apps-api] Add support for topLevelOrigin and paymentRequestOrigin (#130) (Thursday, 13 April)
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Wednesday, 12 April)
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Wednesday, 12 April)
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Wednesday, 12 April)
Re: [w3c/browser-payment-api] Define expected behavior when no 'shippingaddresschange ' event listener is defined (#507) (Tuesday, 11 April)
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) (Monday, 10 April)
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) (Monday, 10 April)
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) (Monday, 10 April)
[w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) (Monday, 10 April)
Re: [w3c/browser-payment-api] Define expected behavior when no 'shippingaddresschange ' event listener is defined (#507) (Friday, 7 April)
Re: [w3c/browser-payment-api] Provide better mapping between PaymentAddress and HTML5 autofill (#505) (Friday, 7 April)
Re: [w3c/webpayments-payment-apps-api] Image object is undefined (#125) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] `appRequest` attribute should not be a dictionary (#111) (Tuesday, 4 April)
Re: [w3c/webpayments-payment-apps-api] `appRequest` attribute should not be a dictionary (#111) (Tuesday, 4 April)
Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) (Monday, 3 April)
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Monday, 3 April)
Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) (Monday, 3 April)

rvm4

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

Salvador de la Puente González

Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) (Wednesday, 12 April)

Tommy Thorsen

Re: [w3c/webpayments-methods-card] What if the card type is unknown by the payment app? (#19) (Wednesday, 19 April)
Re: [w3c/webpayments-methods-card] What if the card type is unknown by the payment app? (#19) (Wednesday, 19 April)
Re: [w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109) (Sunday, 9 April)
Re: [w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109) (Sunday, 9 April)
Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Sunday, 9 April)
Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) (Sunday, 9 April)

Zach Koch

Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) (Friday, 28 April)
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) (Friday, 28 April)
Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) (Wednesday, 26 April)
Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23) (Wednesday, 19 April)
Re: [w3c/webpayments-methods-card] Say how we integrate with PaymentRequest (#23) (Wednesday, 19 April)
Re: [w3c/webpayments-methods-card] What if the card type is unknown by the payment app? (#19) (Wednesday, 19 April)
Re: [w3c/webpayments-methods-card] Clarify this specification is intended to become a W3C Note (#27) (Wednesday, 19 April)
Re: [w3c/webpayments-methods-card] Add an excludedFields BasicCardRequest parameter (#29) (Wednesday, 19 April)
Re: [w3c/webpayments-methods-card] security and privacy considerations section seems insufficient (#31) (Wednesday, 19 April)
Re: [w3c/webpayments-methods-card] security and privacy considerations section seems insufficient (#31) (Wednesday, 19 April)
Re: [w3c/webpayments-method-identifiers] Why are payment ids restricted to [a-z0-9]? (#20) (Wednesday, 19 April)
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) (Wednesday, 19 April)
Re: [w3c/webpayments-method-identifiers] citation to dated version of since-abandoned url spec fork is unusual (#30) (Wednesday, 19 April)
Re: [w3c/browser-payment-api] Edits for issue 481 (#506) (Wednesday, 12 April)
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) (Wednesday, 12 April)
Re: [w3c/browser-payment-api] Provide better mapping between PaymentAddress and HTML5 autofill (#505) (Wednesday, 12 April)
Re: [w3c/browser-payment-api] Define expected behavior when no 'shippingaddresschange ' event listener is defined (#507) (Wednesday, 12 April)
Re: [w3c/browser-payment-api] Supplement QuoteExceededError with NotAllowedError for canMakePayments (#485) (Wednesday, 5 April)
Re: [w3c/browser-payment-api] Use "NotAllowedError" instead of "QuotaExceededError" (#488) (Wednesday, 5 April)
Re: [w3c/browser-payment-api] Editors to figure out text on line items (#477) (Wednesday, 5 April)
Re: [w3c/browser-payment-api] State change issues in updateWith() (#500) (Wednesday, 5 April)
Re: [w3c/browser-payment-api] State change issues in updateWith() (#500) (Wednesday, 5 April)

Last message date: Friday, 28 April 2017 15:51:41 UTC