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

Friday, 28 April 2017

Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Domenic Denicola
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Domenic Denicola
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Domenic Denicola
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Domenic Denicola
[w3c/browser-payment-api] Redo PR 506 (on merchant prefs) (#518) ianbjacobs
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) ianbjacobs
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) ianbjacobs
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Zach Koch
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) Zach Koch
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Domenic Denicola
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Domenic Denicola
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/browser-payment-api] Editorial: consider removing merchant preference language (#506) Marcos Cáceres

Thursday, 27 April 2017

Re: [w3c/browser-payment-api] Editorial: consider removing merchant preference language (#506) ianbjacobs
Re: [w3c/browser-payment-api] Editorial: consider removing merchant preference language (#506) Marcos Cáceres
Re: [w3c/browser-payment-api] Editorial: consider removing merchant preference language (#506) ianbjacobs
Re: [w3c/browser-payment-api] Editorial: consider removing merchant preference language (#506) ianbjacobs
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) ianbjacobs
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) ianbjacobs
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Domenic Denicola
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512) Domenic Denicola
Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) Edouard Chin
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) ianbjacobs
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) ianbjacobs
Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) Rouslan Solomakhin
Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) Edouard Chin
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Anne van Kesteren
Re: [w3c/browser-payment-api] supportedMethods (URL and DOMString) (#464) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) ianbjacobs
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Anne van Kesteren
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Anne van Kesteren
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Anne van Kesteren
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Anne van Kesteren
Re: [w3c/webpayments-method-identifiers] [SECURE-CONTEXTS] should be a normative rather than informative reference (#29) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Anne van Kesteren
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Anne van Kesteren
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Anne van Kesteren
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Anne van Kesteren
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Anne van Kesteren
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Anne van Kesteren
Re: [w3c/webpayments-method-identifiers] [SECURE-CONTEXTS] should be a normative rather than informative reference (#29) Marcos Cáceres
Re: [w3c/browser-payment-api] Editorial: event `.target` attribute should be relatedTarget (#513) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) ianbjacobs
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] [SECURE-CONTEXTS] should be a normative rather than informative reference (#29) ianbjacobs
Re: [w3c/webpayments-method-identifiers] [SECURE-CONTEXTS] should be a normative rather than informative reference (#29) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) ianbjacobs
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] Payment Method Identifier needs dfn (#23) Marcos Cáceres
[w3c/webpayments-method-identifiers] editorial: rm 'Conditional Matching Beyond Payment Methods' section (#36) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) ianbjacobs
Re: [w3c/webpayments-method-identifiers] Remove "Conditional Matching Beyond Payment Method Identifier Matching" (#34) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) ianbjacobs
Re: [w3c/webpayments-method-identifiers] [SECURE-CONTEXTS] should be a normative rather than informative reference (#29) ianbjacobs
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] Remove "Conditional Matching Beyond Payment Method Identifier Matching" (#34) ianbjacobs
Re: [w3c/webpayments-method-identifiers] If URL parsing fails then always fail to match URLs. (#31) Marcos Cáceres
[w3c/webpayments-method-identifiers] feat: rewrite all the things (#35) Marcos Cáceres
Re: [w3c/browser-payment-api] Remove 2119 language from privacy section. (#511) ianbjacobs
[w3c/webpayments-method-identifiers] Remove "Conditional Matching Beyond Payment Method Identifier Matching" (#34) Marcos Cáceres
[w3c/webpayments-method-identifiers] Removed wording about overloading identifiers (#33) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] If URL parsing fails then always fail to match URLs. (#31) Anne van Kesteren
Re: [w3c/browser-payment-api] editorial: use DOM relatedTarget instead of .target (closes #513) (#515) Marcos Cáceres
Re: [w3c/browser-payment-api] editorial: use DOM relatedTarget instead of .target (closes #513) (#515) Marcos Cáceres
Re: [w3c/browser-payment-api] editorial: s/target/request in updateWith() algo (#517) Marcos Cáceres
Re: [w3c/browser-payment-api] editorial: xref EventInit in DOM spec (#514) Marcos Cáceres
Re: [w3c/browser-payment-api] Remove 2119 language from privacy section. (#511) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] If URL parsing fails then always fail to match URLs. (#31) Marcos Cáceres
[w3c/webpayments-method-identifiers] "W3C String" is overly generic (#32) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] SRI on manifest (#18) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] SRI on manifest (#18) Marcos Cáceres
Re: [w3c/webpayments-method-identifiers] [SECURE-CONTEXTS] should be a normative rather than informative reference (#29) Marcos Cáceres
Re: [w3c/browser-payment-api] editorial: s/target/request in updateWith() algo (#517) Domenic Denicola
Re: [w3c/browser-payment-api] editorial: use DOM relatedTarget instead of .target (closes #513) (#515) Domenic Denicola
Re: [w3c/browser-payment-api] editorial: xref EventInit in DOM spec (#514) Domenic Denicola
Re: [w3c/browser-payment-api] Remove 2119 language from privacy section. (#511) Domenic Denicola
[w3c/browser-payment-api] editorial: s/target/request in updateWith() algo (#516) Marcos Cáceres
Re: [w3c/browser-payment-api] Editorial: event `.target` attribute should be relatedTarget (#513) Marcos Cáceres
Re: [w3c/browser-payment-api] editorial: s/target/request in updateWith() algo (#516) Marcos Cáceres
[w3c/browser-payment-api] editorial: s/target/request in updateWith() algo (#517) Marcos Cáceres
Re: [w3c/browser-payment-api] editorial: s/target/request in updateWith() algo (#516) Marcos Cáceres
Re: [w3c/browser-payment-api] 'Interactive' Bias in API (#467) Marcos Cáceres
Re: [w3c/browser-payment-api] 'Interactive' Bias in API (#467) Marcos Cáceres
[w3c/browser-payment-api] editorial: use DOM relatedTarget instead of .target (closes #513) (#515) Marcos Cáceres
[w3c/browser-payment-api] editorial: xref EventInit in DOM spec (#514) Marcos Cáceres
[w3c/browser-payment-api] Editorial: event `.target` attribute should be relatedTarget (#513) Marcos Cáceres
Re: [w3c/browser-payment-api] Remove 2119 language from privacy section. (#511) Ade Bateman
[w3c/browser-payment-api] Reject with SecurityError if the UA rejects the call to show(). (#512) Ade Bateman
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) Ade Bateman
Re: [w3c/browser-payment-api] Editorial: consider removing merchant preference language (#506) Marcos Cáceres
Re: [w3c/browser-payment-api] Remove 2119 language from privacy section. (#511) Marcos Cáceres

Wednesday, 26 April 2017

Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) Zach Koch
Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) Rouslan Solomakhin
Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) Edouard Chin
Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) Rouslan Solomakhin
Re: [w3c/browser-payment-api] canMakePayment() might be in the wrong place? (#403) Edouard Chin
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) Ade Bateman
Re: [w3c/browser-payment-api] 'Interactive' Bias in API (#467) Ade Bateman
[w3c/browser-payment-api] Remove 2119 language from privacy section. (#511) Ade Bateman
Re: [w3c/browser-payment-api] Define expected behavior when no 'shippingaddresschange ' event listener is defined (#507) Domenic Denicola
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) Domenic Denicola
Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) Marcos Cáceres
Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) Jeff Burdges
Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) Marcos Cáceres
Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) Jeff Burdges
Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) Marcos Cáceres

Tuesday, 25 April 2017

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

Monday, 24 April 2017

Friday, 21 April 2017

Re: [w3c/webpayments-payment-handler] Merge PaymentAppResponse and PaymentRequestEvent (#142) ianbjacobs

Thursday, 20 April 2017

Re: [w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#18) ianbjacobs
Re: [w3c/webpayments-method-identifiers] If URL parsing fails then always fail to match URLs. (#31) Ade Bateman
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) ianbjacobs
Re: [w3c/webpayments-method-identifiers] If URL parsing fails then always fail to match URLs. (#31) Adrian Hope-Bailie
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Edits for issue 481 (#506) Nick Telford-Reed
Re: [w3c/browser-payment-api] Edits for issue 481 (#506) mattsaxon
[w3c/webpayments-method-identifiers] If URL parsing fails then always fail to match URLs. (#31) Ade Bateman
Re: [w3c/webpayments-methods-card] Add an excludedFields BasicCardRequest parameter (#29) mattsaxon
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) ianbjacobs
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) Adrian Hope-Bailie
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) ianbjacobs
Re: [w3c/webpayments-method-identifiers] Link to registry of W3C-published short strings (#26) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127) mattsaxon
Re: [w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127) mattsaxon
Re: [w3c/browser-payment-api] Missing (normative) reference to BPC-47 (language code) (#503) Marcos Cáceres
Re: [w3c/browser-payment-api] Added BCP ref (#510) Marcos Cáceres
Re: [w3c/browser-payment-api] Added BCP ref (#510) Marcos Cáceres
Re: [w3c/browser-payment-api] Added BCP ref (#510) Marcos Cáceres
Re: [w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#18) ianbjacobs

Wednesday, 19 April 2017

Tuesday, 18 April 2017

Re: [w3c/webpayments-payment-handler] respec fix (#141) ianbjacobs
Re: [w3c/webpayments-payment-handler] respec fix (#141) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] respec fix (#141) ianbjacobs
[w3c/webpayments-payment-handler] respec fix (#141) ianbjacobs
Re: [w3c/webpayments-payment-handler] Improve payment app arch image (#140) ianbjacobs
Re: [w3c/webpayments-payment-handler] Improve payment app arch image (#140) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Improve payment app arch image (#140) ianbjacobs
Re: [w3c/webpayments-payment-handler] Define event handler before payment manager (#134) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Improve payment app arch image (#140) Adrian Hope-Bailie
[w3c/webpayments-payment-handler] Improve payment app arch image (#140) ianbjacobs
Re: [w3c/webpayments-payment-handler] Passing modifiers to payment apps (#139) Rouslan Solomakhin
Re: [w3c/webpayments-payment-handler] Passing modifiers to payment apps (#139) Rouslan Solomakhin
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) Dave Longley
Re: [w3c/webpayments-payment-handler] Passing modifiers to payment apps (#139) ianbjacobs
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) ianbjacobs
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) Adrian Hope-Bailie
[w3c/webpayments-payment-handler] Passing modifiers to payment apps (#139) Rouslan Solomakhin
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) ianbjacobs
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Do we need "Payment Manager" and "Payment Handler"? (#127) mattsaxon

Monday, 17 April 2017

Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) ianbjacobs
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) ianbjacobs
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) ianbjacobs
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) ianbjacobs
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) ianbjacobs
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) ianbjacobs
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) ianbjacobs
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) ianbjacobs
Re: [w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) ianbjacobs
[w3c/webpayments-payment-handler] Editorial changes for FPWD (#138) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Tidy (#137) ianbjacobs
Re: [w3c/webpayments-payment-handler] Tidy (#137) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-handler] Tidy (#137) Adrian Hope-Bailie
[w3c/webpayments-payment-handler] Tidy (#137) ianbjacobs
Re: [w3c/webpayments-payment-handler] Update README.md to link to new repo (#135) ianbjacobs
Re: [w3c/webpayments-payment-handler] Updated short name and URL for new repo name (#136) ianbjacobs
Re: [w3c/webpayments-payment-handler] Update README.md to link to new repo (#135) ianbjacobs
Re: [w3c/webpayments-payment-handler] Updated short name and URL for new repo name (#136) Adrian Hope-Bailie
[w3c/webpayments-payment-handler] Updated short name and URL for new repo name (#136) ianbjacobs
[w3c/webpayments-payment-handler] Update README.md to link to new repo (#135) Adrian Hope-Bailie

Saturday, 15 April 2017

Re: [w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) Marcos Cáceres
Re: [w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) Marcos Cáceres
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) Marcos Cáceres
Re: [w3c/webpayments-payment-apps-api] Define event handler before payment manager (#134) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) Marcos Cáceres
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) Marcos Cáceres
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) Marcos Cáceres
Re: [w3c/browser-payment-api] Define expected behavior when no 'shippingaddresschange ' event listener is defined (#507) Marcos Cáceres

Friday, 14 April 2017

Re: [w3c/browser-payment-api] Define expected behavior when no 'shippingaddresschange ' event listener is defined (#507) Matt Gaunt
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Define event handler before payment manager (#134) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) Adrian Hope-Bailie
[w3c/webpayments-payment-apps-api] Define event handler before payment manager (#134) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Do we need "Payment Manager" and "Payment Handler"? (#127) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Define expected behavior when no 'shippingaddresschange ' event listener is defined (#507) Matt Gaunt
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) Marcos Cáceres

Thursday, 13 April 2017

[w3c/webpayments-payment-apps-api] Issue marker cleanup (#133) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Multiple payment apps per origin (#98) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Pictures would help! (#49) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Diagrams (#132) ianbjacobs
[w3c/webpayments-payment-apps-api] Diagrams (#132) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Do we need "Payment Manager" and "Payment Handler"? (#127) Rouslan Solomakhin
Re: [w3c/webpayments-payment-apps-api] WebIDL fix (#131) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Add support for topLevelOrigin and paymentRequestOrigin (#130) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Add support for topLevelOrigin and paymentRequestOrigin (#130) Rouslan Solomakhin
Re: [w3c/webpayments-payment-apps-api] WebIDL fix (#131) Rouslan Solomakhin
Re: [w3c/webpayments-payment-apps-api] Add support for topLevelOrigin and paymentRequestOrigin (#130) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Add support for topLevelOrigin and paymentRequestOrigin (#130) Rouslan Solomakhin
Re: [w3c/webpayments-payment-apps-api] Add support for topLevelOrigin and paymentRequestOrigin (#130) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Add support for topLevelOrigin and paymentRequestOrigin (#130) frank-hoffmann
[w3c/webpayments-payment-apps-api] WebIDL fix (#131) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120) ianbjacobs
[w3c/webpayments-payment-apps-api] Add support for topLevelOrigin and paymentRequestOrigin (#130) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Add .clear() to map-likes (#129) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] [Editorial] Clean up respec errors (#122) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] [Editorial] Clean up respec errors (#122) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) Marcos Cáceres
[w3c/webpayments-payment-apps-api] Add .clear() to map-likes (#129) Marcos Cáceres
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) Marcos Cáceres
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) Marcos Cáceres

Wednesday, 12 April 2017

Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) ianbjacobs
[w3c/webpayments-payment-apps-api] Revisit Examples 3 and 4 (#128) ianbjacobs
[w3c/webpayments-payment-apps-api] Do we need "Payment Manager" and "Payment Handler"? (#127) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) ianbjacobs
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) Ade Bateman
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) ianbjacobs
Re: [w3c/browser-payment-api] Edits for issue 481 (#506) Zach Koch
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) Zach Koch
Re: [w3c/browser-payment-api] Provide better mapping between PaymentAddress and HTML5 autofill (#505) Zach Koch
Re: [w3c/browser-payment-api] Define expected behavior when no 'shippingaddresschange ' event listener is defined (#507) Zach Koch
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) ianbjacobs
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Unclear what happens when multiple PRs call show() (#462) Marcos Cáceres
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) Marcos Cáceres
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) Salvador de la Puente González

Tuesday, 11 April 2017

Monday, 10 April 2017

Re: [w3c/browser-payment-api] Edits for issue 481 (#506) Marcos Cáceres
Re: [w3c/browser-payment-api] Edits for issue 481 (#506) Marcos Cáceres
Re: [w3c/browser-payment-api] Edits for issue 481 (#506) Marcos Cáceres
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) Rouslan Solomakhin
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) Jinho Bang
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) Domenic Denicola
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) Rouslan Solomakhin
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) Rouslan Solomakhin
[w3c/browser-payment-api] Editorial: paymentResponse.complete() should return a rejected promise, not throw (#509) Domenic Denicola
Re: [w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) Domenic Denicola
[w3c/browser-payment-api] "User accepts payment request" algorithm should timeout without .complete(). (#508) Rouslan Solomakhin

Sunday, 9 April 2017

Re: [w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109) Tommy Thorsen
Re: [w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109) Tommy Thorsen
Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) Tommy Thorsen
Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) Tommy Thorsen

Friday, 7 April 2017

Thursday, 6 April 2017

Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) ianbjacobs
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) Dave Longley
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) Marcos Cáceres
Re: [w3c/webpayments-payment-apps-api] Relation between merchant order of payment methods and payment app order of instruments (#116) KJM
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) Dave Longley
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) Marcos Cáceres
Re: [w3c/browser-payment-api] should .show() be user gated? (#486) Marcos Cáceres
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) Marcos Cáceres
Re: [w3c/webpayments-payment-apps-api] Respec fixes (#126) Marcos Cáceres

Wednesday, 5 April 2017

Tuesday, 4 April 2017

Re: [w3c/browser-payment-api] Editors to figure out text on line items (#477) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Relation between merchant order of payment methods and payment app order of instruments (#116) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Image object is undefined (#125) Rouslan Solomakhin
Re: [w3c/webpayments-payment-apps-api] Pictures would help! (#49) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Recommended payment apps (#74) ianbjacobs
[w3c/webpayments-payment-apps-api] Image object is undefined (#125) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] What does "icon" mean? (#69) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] What does "icon" mean? (#69) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] What is a Payment App? (#105) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Origin should include iframe(s) (#120) Rouslan Solomakhin
Re: [w3c/webpayments-payment-apps-api] Support for Abort() being delegated to Payment Handler (#117) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Support for Abort() being delegated to Payment Handler (#117) mattsaxon
Re: [w3c/webpayments-payment-apps-api] `appRequest` attribute should not be a dictionary (#111) Rouslan Solomakhin
Re: [w3c/webpayments-payment-apps-api] `appRequest` attribute should not be a dictionary (#111) Rouslan Solomakhin
Re: [w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121) Marcos Cáceres
Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] [Privacy] Clarify what information user agents forget at various moments (#124) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] [Privacy] Clarify what information user agents forget at various moments (#124) Marcos Cáceres
Re: [w3c/browser-payment-api] Clarify use of API in (or not in) Secure Contexts (#501) Marcos Cáceres
Re: [w3c/browser-payment-api] Clarify use of API in (or not in) Secure Contexts (#501) Marcos Cáceres
Re: [w3c/browser-payment-api] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) mattsaxon
Re: [w3c/browser-payment-api] Consider adding examples of payment matching algorithm (#498) Marcos Cáceres
Re: [w3c/webpayments-methods-card] Add an excludedFields BasicCardRequest parameter (#29) Marcos Cáceres
Re: [w3c/webpayments-methods-card] Add an excludedFields BasicCardRequest parameter (#29) mattsaxon
Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) mattsaxon
Re: [w3c/browser-payment-api] 'Pull' Payment Bias in API spec (#499) mattsaxon
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) Marcos Cáceres
Re: [w3c/browser-payment-api] fix: broken links to HTML (closes #502) (#504) Marcos Cáceres
Re: [w3c/browser-payment-api] Reference to payment apps in Introduction needs updating (#496) Marcos Cáceres
Re: [w3c/browser-payment-api] fix: broken links to HTML (closes #502) (#504) Domenic Denicola
[w3c/browser-payment-api] fix: broken links to HTML (closes #502) (#504) Marcos Cáceres
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) Domenic Denicola
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) Marcos Cáceres
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) Marcos Cáceres
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) Domenic Denicola
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) Marcos Cáceres
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) Domenic Denicola
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) Marcos Cáceres
Re: [w3c/browser-payment-api] Links to some HTML definitions are broken (#502) Marcos Cáceres
Re: [w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121) Marcos Cáceres
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) Marcos Cáceres
Re: [w3c/browser-payment-api] Add extension point (#492) Marcos Cáceres
Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) Marcos Cáceres
Re: [w3c/browser-payment-api] Adding legal entity types for consistency (#491) Marcos Cáceres
Re: [w3c/browser-payment-api] Adding legal entity types for consistency (#491) Marcos Cáceres
Re: [w3c/browser-payment-api] Adding legal entity types for consistency (#491) Marcos Cáceres
Re: [w3c/browser-payment-api] PaymentAddress and null values (#495) Marcos Cáceres
Re: [w3c/browser-payment-api] PaymentAddress and null values (#495) Domenic Denicola
Re: [w3c/browser-payment-api] PaymentAddress and null values (#495) Marcos Cáceres
Re: [w3c/browser-payment-api] PaymentAddress and null values (#495) Domenic Denicola
Re: [w3c/browser-payment-api] Add extension point (#492) Adrian Hope-Bailie
[w3c/browser-payment-api] Missing (normative) reference to BPC-47 (language code) (#503) ianbjacobs

Monday, 3 April 2017

[w3c/browser-payment-api] Links to some HTML definitions are broken (#502) Nick Doty
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add extension point (#492) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add extension point (#492) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Display may be subject to user and local policy (consider UA making security decisions etc) (#5) ianbjacobs
Re: [w3c/browser-payment-api] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] Share user data with Payment App (#123) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Payment App or Payment Handler language (#497) ianbjacobs
Re: [w3c/browser-payment-api] Reference to payment apps in Introduction needs updating (#496) ianbjacobs
Re: [w3c/browser-payment-api] 'Pull' Payment Bias in API spec (#499) ianbjacobs
Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) ianbjacobs
[w3c/webpayments-methods-card] Add an excludedFields BasicCardRequest parameter (#29) ianbjacobs
Re: [w3c/browser-payment-api] Add extension point (#492) ianbjacobs
Re: [w3c/browser-payment-api] Add extension point (#492) ianbjacobs
Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121) adamroach
Re: [w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121) ianbjacobs
Re: [w3c/webpayments-payment-apps-api] The instrumnets/wallets attributes should be readonly and [SameObject]. (#121) Jinho Bang
Re: [w3c/browser-payment-api] Clarify use of API in (or not in) Secure Contexts (#501) ianbjacobs
Re: [w3c/browser-payment-api] Clarify use of API in (or not in) Secure Contexts (#501) ianbjacobs
Re: [w3c/browser-payment-api] Clarify use of API in (or not in) Secure Contexts (#501) Marcos Cáceres
[w3c/webpayments-payment-apps-api] [Privacy] Clarify what information user agents forget at various moments (#124) ianbjacobs
[w3c/browser-payment-api] Clarify use of API in (or not in) Secure Contexts (#501) ianbjacobs
Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) mattsaxon
Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) Rouslan Solomakhin
Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) mattsaxon
Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) Rouslan Solomakhin
[w3c/browser-payment-api] State change issues in updateWith() (#500) mattsaxon
[w3c/browser-payment-api] 'Pull' Payment Bias in API spec (#499) mattsaxon
Re: [w3c/browser-payment-api] Payment App or Payment Handler language (#497) mattsaxon
[w3c/browser-payment-api] Consider adding examples of payment matching algorithm (#498) mattsaxon
[w3c/browser-payment-api] Payment App or Payment Handler language (#497) mattsaxon
[w3c/browser-payment-api] Reference to payment apps in Introduction needs updating (#496) mattsaxon
Re: [w3c/browser-payment-api] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) Matt Saxon
Re: [w3c/webpayments-methods-card] Clarify the required behaviour for options parameters (#26) Matt Saxon
Re: [w3c/browser-payment-api] PaymentAddress and null values (#495) Marcos Cáceres
Re: [w3c/browser-payment-api] PaymentAddress and null values (#495) Marcos Cáceres
Re: [w3c/browser-payment-api] PaymentAddress and null values (#495) Marcos Cáceres
[w3c/browser-payment-api] ShippingAddress and null values (#495) Marcos Cáceres
Re: [w3c/webpayments-payment-apps-api] Share user data with Payment App (#123) Marcos Cáceres
Re: [w3c/browser-payment-api] maybe add `DisplayItem` dictionary (#457) Marcos Cáceres
Re: [w3c/browser-payment-api] Add postMessage() and addMessageListener() for enabling "in-bound" communication (#494) Marcos Cáceres
Re: [w3c/browser-payment-api] Add postMessage() and addMessageListener() for enabling "in-bound" communication (#494) Anders Rundgren
Re: [w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) Marcos Cáceres
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) Marcos Cáceres
Re: [w3c/browser-payment-api] Add extension point (#492) Marcos Cáceres
Re: [w3c/browser-payment-api] Add extension point (#492) Marcos Cáceres
Re: [w3c/browser-payment-api] Add explicit extension point to matching algo (#470) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add postMessage() and addMessageListener() for enabling "in-bound" communication (#494) Adrian Hope-Bailie

Sunday, 2 April 2017

Saturday, 1 April 2017

[w3c/browser-payment-api] Standardize on "Payer" and "Payee" terms (#493) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] maybe add `DisplayItem` dictionary (#457) Adrian Hope-Bailie
Re: [w3c/webpayments-payment-apps-api] Share user data with Payment App (#123) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should user agent validate currency? (#490) Adrian Hope-Bailie
Re: [w3c/webpayments-methods-card] Leave Off Unneeded Information (#5) Adrian Hope-Bailie
[w3c/browser-payment-api] Add extension point (#492) Adrian Hope-Bailie

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