public-webpayments-specs@w3.org from November 2016 by date

Wednesday, 30 November 2016

• Re: [w3c/browser-payment-api] Making this API work with HTML Forms (#330) Zach Koch
• Re: [w3c/browser-payment-api] Supporting push payment methods (#224) ianbjacobs
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) rvm4
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) stan-stripe
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) rvm4
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) Rick Byers
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) Boris Zbarsky
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) Boris Zbarsky
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) Boris Zbarsky
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) Rick Byers
• Re: [w3c/browser-payment-api] editorial: PaymentRequest ctor, describe errors (closes #290) (#355) Zach Koch
• Re: [w3c/browser-payment-api] editorial: PaymentRequest ctor, describe errors (closes #290) (#355) Ade Bateman
• Re: [w3c/browser-payment-api] normative(PaymentComplete): replace '' with 'unknown' (closes #308) (#312) Zach Koch
• Re: [w3c/browser-payment-api] editorial: clarify examples (#329) Ade Bateman
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) Rick Byers
• Re: [w3c/webpayments-payment-apps-api] Analyse security properties of payment app execution environment (#23) ianbjacobs
• [w3c/browser-payment-api] editorial: PaymentRequest ctor, describe error (closes #290) (#355) Marcos Cáceres
• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) Anne van Kesteren
• [w3c/browser-payment-api] Ambiguous conformance requirement in constructor (#354) Marcos Cáceres
• [w3c/browser-payment-api] "store" value in [[internalSlot]] (#353) Marcos Cáceres
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Anne van Kesteren
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Marcos Cáceres
• Re: [w3c/webpayments-payment-apps-api] What does "icon" mean? (#69) Marcos Cáceres
• Re: [w3c/browser-payment-api] Is section 3.4 informative or normative? (#342) Marcos Cáceres
• Re: [w3c/browser-payment-api] Is section 3.4 informative or normative? (#342) Boris Zbarsky
• Re: [w3c/browser-payment-api] What is the shippingAddress/shippingOption of a PaymentResponse if requestShipping was false? (#352) Boris Zbarsky
• [w3c/browser-payment-api] What is the shippingAddress of a PaymentResponse if requestShipping was false? (#352) Boris Zbarsky
• [w3c/browser-payment-api] The shipping address/option changed algorithms should not be synchronously poking internal slots (#351) Boris Zbarsky
• [w3c/browser-payment-api] updateWith will silently ignore data in hard-to-debug ways (#350) Boris Zbarsky
• Re: [w3c/browser-payment-api] It's probably a good idea to use https://www.w3.org/2001/tag/doc/promises-guide#shorthand-reacting in updateWith (#348) Marcos Cáceres
• [w3c/browser-payment-api] The "if d is resolved" section of updateWith needs to be more explicit about how it gets a PaymentDetails dictionary (#349) Boris Zbarsky
• [w3c/browser-payment-api] It's probably a good idea to use https://www.w3.org/2001/tag/doc/promises-guide#shorthand-reacting in updateWith (#348) Boris Zbarsky
• [w3c/browser-payment-api] The target of a PaymentRequestUpdateEvent may not be a PaymentRequest object (#347) Boris Zbarsky
• Re: [w3c/browser-payment-api] editorial: clarify examples (#329) Marcos Cáceres
• Re: [w3c/browser-payment-api] What does it mean for a user agent to validate displayItems? (#344) Boris Zbarsky
• Re: [w3c/browser-payment-api] "asynchronously perform the remaining steps" is not defined (#341) Boris Zbarsky
• Re: [w3c/browser-payment-api] The "data" member of PaymentMethodData doesn't seem to actually be used for anything (#338) Boris Zbarsky
• [w3c/browser-payment-api] The "data" member of PaymentDetailsModifier doesn't seem to be used for anything (#346) Boris Zbarsky
• [w3c/browser-payment-api] The shippingOptions field is used in more cases than the spec claims, as far as I can tell (#345) Boris Zbarsky
• Re: [w3c/browser-payment-api] What does it mean for a user agent to validate displayItems? (#344) ianbjacobs
• Re: [w3c/browser-payment-api] How are currency systems expected to be implemented in practice? (#343) Boris Zbarsky
• Re: [w3c/browser-payment-api] "asynchronously perform the remaining steps" is not defined (#341) adamroach
• [w3c/browser-payment-api] What does it mean for a user agent to validate displayItems? (#344) Boris Zbarsky
• Re: [w3c/browser-payment-api] How are currency systems expected to be implemented in practice? (#343) Marcos Cáceres
• [w3c/browser-payment-api] How are currency systems expected to be implemented in practice? (#343) Boris Zbarsky
• [w3c/browser-payment-api] Is section 3.4 informative or normative? (#342) Boris Zbarsky
• [w3c/browser-payment-api] "asynchronously perform the remaining steps" is not defined (#341) Boris Zbarsky
• [w3c/browser-payment-api] Is it intended that abort() rejects the acceptPromise and resolves its return value in separate tasks? (#340) Boris Zbarsky
• [w3c/browser-payment-api] Setting internal slots of objects from asynchronous steps is not OK (#339) Boris Zbarsky
• Re: [w3c/browser-payment-api] The "data" member of PaymentMethodData doesn't seem to actually be used for anything (#338) adamroach
• [w3c/browser-payment-api] The "data" member of PaymentMethodData doesn't seem to actually be used for anything (#338) Boris Zbarsky
• Re: [w3c/browser-payment-api] Please define your internal slot notation before using it (#336) Boris Zbarsky
• Re: [w3c/browser-payment-api] PaymentDetails may not have values present for various sequences, but the PaymentRequest constructor assumes that it does (#333) Boris Zbarsky
• [w3c/browser-payment-api] Why is the "shippingType" member of PaymentOptions not a PaymentShippingType? (#337) Boris Zbarsky
• [w3c/browser-payment-api] Please define your internal slot notation before using it (#336) Boris Zbarsky
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) ojan
• [w3c/browser-payment-api] A PaymentDetailsModifier may not have an additionalDisplayItems value present (#335) Boris Zbarsky
• [w3c/browser-payment-api] A `PaymentItem` can't be a "valid decimal monetary value" (#334) Boris Zbarsky
• Re: [w3c/browser-payment-api] "contains a value for" isn't defined for dictionaries (#321) Boris Zbarsky
• Re: [w3c/browser-payment-api] PaymentDetails may not have values present for various sequences, but the PaymentRequest constructor assumes that it does (#333) Boris Zbarsky
• [w3c/browser-payment-api] PaymentDetails may not have values present for various sequences, but the PaymentRequest constructor assumes that it does (#333) Boris Zbarsky
• [w3c/browser-payment-api] The origin restrictions in the PaymentRequest are not nearly strong enough (#332) Boris Zbarsky
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) Boris Zbarsky
• Re: [w3c/browser-payment-api] PaymentDetails "total" member should be required (#320) Boris Zbarsky
• Re: [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) Ade Bateman
• Re: [w3c/browser-payment-api] PaymentDetails "total" member should be required (#320) Ade Bateman

Tuesday, 29 November 2016

• Re: [w3c/browser-payment-api] PaymentDetails "total" member should be required (#320) Philip Jägenstedt
• Re: [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) ianbjacobs
• Re: [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) Ade Bateman
• Re: [w3c/browser-payment-api] PaymentDetails "total" member should be required (#320) Ade Bateman
• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) Ade Bateman
• Re: [w3c/browser-payment-api] chore: xref internal slots (#319) Ade Bateman
• Re: [w3c/browser-payment-api] Fix example (#318) Ade Bateman
• Re: [w3c/browser-payment-api] PaymentDetails "total" member should be required (#320) Philip Jägenstedt
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] What does "icon" mean? (#69) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] (Promise<PaymentResponse> or PaymentResponse) is invalid Web IDL. (#71) ianbjacobs

Monday, 28 November 2016

• Re: [w3c/browser-payment-api] Collect Privacy and Security considerations (#331) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) ianbjacobs
• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) Michael[tm] Smith
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Marcos Cáceres
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Marcos Cáceres
• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) Marcos Cáceres
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) Marcos Cáceres

Sunday, 27 November 2016

• Re: [w3c/webpayments-payment-apps-api] Modify section 10.4 Payment App Response to allow an app to cancel. (#72) Adrian Hope-Bailie

Saturday, 26 November 2016

• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) Michael[tm] Smith
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) Nick Shearer

Friday, 25 November 2016

• Re: [w3c/webpayments-payment-apps-api] How can a Browser-based Payment App cancel the payment flow? (#37) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Modify section 10.4 Payment App Response to allow an app to cancel. (#72) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Modify section 10.4 Payment App Response to allow an app to cancel. (#72) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Modify section 10.4 Payment App Response to allow an app to cancel. (#72) ianbjacobs
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) Jeff Burdges
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Jake Archibald
• Re: [w3c/webpayments-payment-apps-api] Modify section 10.4 Payment App Response to allow an app to cancel. (#72) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Modify section 10.4 Payment App Response to allow an app to cancel. (#72) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) Marcos Cáceres
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) Nick Shearer

Thursday, 24 November 2016

• Re: [w3c/webpayments-payment-apps-api] How can a Browser-based Payment App cancel the payment flow? (#37) Tommy Thorsen
• [w3c/webpayments-payment-apps-api] Modify section 10.4 Payment App Response to allow an app to cancel. (#72) Tommy Thorsen
• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) Nick Shearer
• Re: [w3c/browser-payment-api] Making this API work with HTML Forms (#330) Marcos Cáceres
• Re: [w3c/browser-payment-api] Making this API work with HTML Forms (#330) Rouslan Solomakhin
• [w3c/browser-payment-api] Collect Privacy and Security considerations (#331) Marcos Cáceres
• Re: [w3c/browser-payment-api] Examples in the spec (#274) Marcos Cáceres
• Re: [w3c/browser-payment-api] Making this API work with HTML Forms (#330) Marcos Cáceres
• [w3c/browser-payment-api] Making this API work with HTML Forms (#330) Marcos Cáceres
• [w3c/browser-payment-api] editorial: clarify examples (#329) Marcos Cáceres
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Marcos Cáceres
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) Marcos Cáceres
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) Marcos Cáceres
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) Marcos Cáceres

Wednesday, 23 November 2016

• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Ilya Grigorik
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] What does "icon" mean? (#69) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] How can a Browser-based Payment App cancel the payment flow? (#37) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] How can a Browser-based Payment App cancel the payment flow? (#37) Rouslan Solomakhin
• [w3c/webpayments-methods-card] Behavior when method-specific data is invalid (#20) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] What does "icon" mean? (#69) ianbjacobs
• Re: [w3c/browser-payment-api] PaymentResponse's details could lead to problems (#328) Marcos Cáceres
• Re: [w3c/browser-payment-api] PaymentResponse's details could lead to problems (#328) Marcos Cáceres
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Marcos Cáceres
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Philip Jägenstedt
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Philip Jägenstedt
• [w3c/browser-payment-api] PaymentResponse's details (#328) Marcos Cáceres
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Tommy Thorsen
• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) Marcos Cáceres
• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) Anne van Kesteren
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) Marcos Cáceres
• Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) Marcos Cáceres
• [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) Marcos Cáceres
• [w3c/browser-payment-api] PaymentOptions seems overly verbose (#326) Marcos Cáceres
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Marcos Cáceres

Tuesday, 22 November 2016

• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Elliott Sprehn
• Re: [w3c/webpayments-payment-apps-api] (Promise<PaymentResponse> or PaymentResponse) is invalid Web IDL. (#71) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] (Promise<PaymentResponse> or PaymentResponse) is invalid Web IDL. (#71) adamroach
• [w3c/browser-payment-api] Should values for supportedNetworks be defined in Basic Card or separately? (#325) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] (Promise<PaymentResponse> or PaymentResponse) is invalid Web IDL. (#71) ianbjacobs
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) raymeskhoury

Monday, 21 November 2016

• [w3c/webpayments-payment-apps-api] (Promise<PaymentResponse> or PaymentResponse) is invalid Web IDL. (#71) Jinho Bang
• [w3c/browser-payment-api] Browsing contexts don't have an "origin" (#324) Boris Zbarsky
• [w3c/browser-payment-api] What is "the script calling the constructor"? (#323) Boris Zbarsky
• [w3c/browser-payment-api] DOMStrings don't contain "characters" (#322) Boris Zbarsky
• [w3c/browser-payment-api] "contains a value for" isn't defined for dictionaries (#321) Boris Zbarsky
• [w3c/browser-payment-api] PaymentDetails "total" member should be required (#320) Boris Zbarsky
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) ianbjacobs
• Re: [w3c/browser-payment-api] chore: xref internal slots (#319) Shane McCarron
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Tommy Thorsen
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] DOMExceptions are now in WebIDL 2 (#314) Marcos Cáceres
• [w3c/browser-payment-api] chore: xref internal slots (#319) Marcos Cáceres
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) Marcos Cáceres
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) Marcos Cáceres
• Re: [w3c/browser-payment-api] enum PaymentComplete's "" (#308) Marcos Cáceres
• Re: [w3c/browser-payment-api] normative(PaymentComplete): replace '' with 'unknown' (closes #308) (#312) Marcos Cáceres

Sunday, 20 November 2016

• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Ian Clelland
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Rouslan Solomakhin
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Adrian Hope-Bailie

Friday, 18 November 2016

• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Tommy Thorsen
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Ilya Grigorik
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Tommy Thorsen
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Rouslan Solomakhin
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Fix example (#318) Marcos Cáceres
• Re: [w3c/browser-payment-api] Fix example (#318) Marcos Cáceres
• Re: [w3c/browser-payment-api] Fix example add inco (#318) ianbjacobs
• [w3c/browser-payment-api] Fix example add inco (#318) Marcos Cáceres
• Re: [w3c/browser-payment-api] Example update (#317) Marcos Cáceres
• Re: [w3c/browser-payment-api] Example update (#317) Marcos Cáceres
• Re: [w3c/browser-payment-api] Example update (#317) Marcos Cáceres
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Marcos Cáceres
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Marcos Cáceres
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Marcos Cáceres
• Re: [w3c/browser-payment-api] Example update (#317) adamroach
• Re: [w3c/browser-payment-api] Example update (#317) Marcos Cáceres
• Re: [w3c/browser-payment-api] Example update (#317) Marcos Cáceres

Thursday, 17 November 2016

• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) ianbjacobs
• [w3c/browser-payment-api] Example update (#317) ianbjacobs
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Jenan Wise
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Nick Shearer
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) ianbjacobs
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) Ade Bateman
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Ade Bateman
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Marijn Kruisselbrink
• Re: [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Marijn Kruisselbrink
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Ade Bateman
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Jenan Wise
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Rouslan Solomakhin
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) ianbjacobs
• Re: [w3c/browser-payment-api] editorial: move monetary value to Definitions sec (closes #303) (#313) Ade Bateman
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) ianbjacobs
• Re: [w3c/browser-payment-api] "valid decimal monetary value" should move to its own section (#303) Ade Bateman
• Re: [w3c/browser-payment-api] editorial: move monetary value to Definitions sec (closes #303) (#313) Ade Bateman
• Re: [w3c/browser-payment-api] normative(PaymentComplete): replace '' with 'unknown' (closes #308) (#312) Ade Bateman
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) ianbjacobs
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Mike West
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] normative(PaymentComplete): replace '' with 'unknown' (closes #308) (#312) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Mike West
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) Shane McCarron
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) adamroach
• [w3c/webpayments-method-identifiers] SRI on manifest (#18) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) Adrian Hope-Bailie
• [w3c/webpayments-method-identifiers] Support for PMI's with schemes other than https? (#17) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] normative(PaymentComplete): replace '' with 'unknown' (closes #308) (#312) Marcos Cáceres
• Re: [w3c/browser-payment-api] Shouldn't HTMLIFrameElement. allowPaymentRequest go into "sandbox"? (#311) Marcos Cáceres
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Jenan Wise
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Marcos Cáceres
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Marcos Cáceres
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Marcos Cáceres
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Marcos Cáceres
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Marcos Cáceres
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Rouslan Solomakhin
• [w3c/browser-payment-api] Detecting Payment Method Availability (#316) Mahesh Kulkarni
• Re: [w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70) Adrian Hope-Bailie
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) Dave Longley
• Re: [w3c/browser-payment-api] editorial: move monetary value to Definitions sec (closes #303) (#313) Marcos Cáceres
• Re: [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) Rouslan Solomakhin

Wednesday, 16 November 2016

• Re: [w3c/browser-payment-api] Merge pull request #1 from w3c/gh-pages (#315) Mahesh Kulkarni
• Re: [w3c/browser-payment-api] Merge pull request #1 from w3c/gh-pages (#315) Mahesh Kulkarni
• [w3c/browser-payment-api] Merge pull request #1 from w3c/gh-pages (#315) Mahesh Kulkarni
• Re: [w3c/browser-payment-api] Behavior for multiple modifiers for the same payment method is not defined (#309) ianbjacobs
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) Ade Bateman
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Versioning (#45) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Pass along a Transaction ID (#47) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Users MUST be able to prevent the display of unregistered payment apps (#59) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Users MUST be able to prevent the display of unregistered payment apps (#59) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] No definition of Open and Proprietary payment methods (#67) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] No definition of Open and Proprietary payment methods (#67) ianbjacobs
• [w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70) ianbjacobs
• [w3c/webpayments-method-identifiers] Update of PMI spec (#16) ianbjacobs
• Re: [w3c/browser-payment-api] "valid decimal monetary value" should move to its own section (#303) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Shouldn't HTMLIFrameElement. allowPaymentRequest go into "sandbox"? (#311) Anne van Kesteren
• [w3c/webpayments-payment-apps-api] What does "icon" mean? (#69) ianbjacobs
• Re: [w3c/browser-payment-api] Shouldn't HTMLIFrameElement. allowPaymentRequest go into "sandbox"? (#311) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Shouldn't HTMLIFrameElement. allowPaymentRequest go into "sandbox"? (#311) Philip Jägenstedt
• Re: [w3c/browser-payment-api] Behavior for multiple modifiers for the same payment method is not defined (#309) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] editorial: move monetary value to Definitions sec (closes #303) (#313) Michael[tm] Smith
• Re: [w3c/browser-payment-api] editorial: move monetary value to Definitions sec (closes #303) (#313) Marcos Cáceres
• Re: [w3c/browser-payment-api] editorial: move monetary value to Definitions sec (closes #303) (#313) Michael[tm] Smith
• Re: [w3c/browser-payment-api] "valid decimal monetary value" should move to its own section (#303) Marcos Cáceres
• Re: [w3c/browser-payment-api] Behavior for multiple modifiers for the same payment method is not defined (#309) Tommy Thorsen
• [w3c/browser-payment-api] DOMExceptions are now in WebIDL 2 (#314) Marcos Cáceres
• [w3c/browser-payment-api] editorial: move monetary value to Definitions sec (closes #303) (#313) Marcos Cáceres
• [w3c/browser-payment-api] normative(PaymentComplete): replace '' with 'unknown' (closes #308) (#312) Marcos Cáceres
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) Marcos Cáceres
• [w3c/browser-payment-api] Shouldn't HTMLIFrameElement. allowPaymentRequest go into "sandbox"? (#311) Marcos Cáceres
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) Marcos Cáceres
• Re: [w3c/browser-payment-api] Tidy up document (#297) Marcos Cáceres
• Re: [w3c/browser-payment-api] chore: fix xrefs and dfns (#296) Marcos Cáceres
• Re: [w3c/browser-payment-api] Relocate conformance section + markup fixes (#295) Marcos Cáceres
• Re: [w3c/browser-payment-api] Combine scope and goal + relocate/reduce conformance (#294) Marcos Cáceres
• Re: [w3c/browser-payment-api] Should PaymentDetails.total be marked as required in IDL? (#300) Marcos Cáceres
• Re: [w3c/browser-payment-api] Should PaymentDetails.total be marked as required in IDL? (#300) Marcos Cáceres
• Re: [w3c/browser-payment-api] Should PaymentDetails.total be marked as required in IDL? (#300) ianbjacobs
• Re: [w3c/browser-payment-api] Relocate conformance section + markup fixes (#295) Marcos Cáceres
• Re: [w3c/browser-payment-api] Combine scope and goal + relocate/reduce conformance (#294) Marcos Cáceres
• Re: [w3c/browser-payment-api] Tidy up document (#297) Marcos Cáceres

Tuesday, 15 November 2016

• Re: [w3c/browser-payment-api] Should PaymentDetails.total be marked as required in IDL? (#300) Marcos Cáceres
• Re: [w3c/browser-payment-api] Response/Request semantics and cancellation (#298) Ade Bateman
• Re: [w3c/browser-payment-api] Tidy up document (#297) Ade Bateman
• Re: [w3c/browser-payment-api] chore: fix xrefs and dfns (#296) Ade Bateman
• Re: [w3c/browser-payment-api] Relocate conformance section + markup fixes (#295) Ade Bateman
• Re: [w3c/browser-payment-api] style(abstract): simplify abstract (#293) Ade Bateman
• Re: [w3c/browser-payment-api] style(abstract): simplify abstract (#293) Ade Bateman
• Re: [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) Shane McCarron
• Re: [w3c/webpayments-payment-apps-api] Display order edits (#68) ianbjacobs
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) Jeff Burdges
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) ianbjacobs
• [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) Marcos Cáceres
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) Marcos Cáceres
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) Marcos Cáceres

Monday, 14 November 2016

• [w3c/browser-payment-api] Behavior for multiple modifiers for the same payment method is not defined (#309) Nick Shearer
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) Shane McCarron
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) Shane McCarron
• Re: [w3c/browser-payment-api] PaymentRequest type checks (valid non-negative monetary value) (#306) Shane McCarron
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) Shane McCarron
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) Shane McCarron
• Re: [w3c/browser-payment-api] Response/Request semantics and cancellation (#298) Marcos Cáceres
• [w3c/browser-payment-api] enum PaymentComplete's "" (#308) Marcos Cáceres
• [w3c/browser-payment-api] The myth of JSON-serializable object (#307) Marcos Cáceres
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) Marcos Cáceres
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] PaymentRequest type checks (valid non-negative monetary value) (#306) Marcos Cáceres
• [w3c/browser-payment-api] PaymentRequest type checks (#306) Marcos Cáceres
• [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) Marcos Cáceres
• [w3c/browser-payment-api] valid decimal monetary value maybe overly restrictive (#304) Marcos Cáceres
• [w3c/browser-payment-api] "valid decimal monetary value" should move to its own section (#303) Marcos Cáceres
• [w3c/browser-payment-api] Why does PaymentRequest constructor throw on details.error (#302) Marcos Cáceres
• [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) Marcos Cáceres
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) stan-stripe
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) Shane McCarron
• [w3c/browser-payment-api] Should PaymentDetails.total be marked as required in IDL? (#300) Marcos Cáceres
• [w3c/browser-payment-api] Data interfaces with serializers (#299) Marcos Cáceres
• [w3c/browser-payment-api] Response/Request semantics and cancellation (#298) Marcos Cáceres
• Re: [w3c/browser-payment-api] PaymentRequest constructor errors should be properly annotated (#290) Marcos Cáceres
• Re: [w3c/browser-payment-api] Dynamic Currency Conversion requirements (#289) Marcos Cáceres
• Re: [w3c/browser-payment-api] Dynamic Currency Conversion requirements (#289) Marcos Cáceres
• Re: [w3c/browser-payment-api] PaymentRequest constructor errors should be properly annotated (#290) Marcos Cáceres
• Re: [w3c/browser-payment-api] Tidy up document (#297) Marcos Cáceres

Sunday, 13 November 2016

• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) Nick Shearer

Friday, 11 November 2016

• [w3c/browser-payment-api] Tidy up document (#297) Marcos Cáceres
• [w3c/browser-payment-api] chore: fix xrefs and dfns (#296) Marcos Cáceres
• Re: [w3c/browser-payment-api] style(abstract): simplify abstract (#293) Marcos Cáceres

Thursday, 10 November 2016

• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) stan-stripe
• Re: [w3c/browser-payment-api] style(abstract): simplify abstract (#293) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Relocate conformance section + markup fixes (#295) Marcos Cáceres
• Re: [w3c/browser-payment-api] Relocate conformance section + markup fixes (#295) Marcos Cáceres
• [w3c/browser-payment-api] Relocate conformance section + markup fixes (#295) Marcos Cáceres
• [w3c/browser-payment-api] Combine scope and goal + relocate/reduce conformance (#294) Marcos Cáceres
• [w3c/browser-payment-api] style(abstract): simplify abstract (#293) Marcos Cáceres

Monday, 7 November 2016

• Re: [w3c/webpayments-payment-apps-api] Display order edits (#68) Adrian Hope-Bailie

Sunday, 6 November 2016

• [w3c/webpayments-payment-apps-api] Display order edits (#68) ianbjacobs

Thursday, 3 November 2016

• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) rvm4
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) rvm4
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) rvm4

Wednesday, 2 November 2016

• [w3c/webpayments-payment-apps-api] No definition of Open and Proprietary payment methods (#67) maxpassion

Tuesday, 1 November 2016

• Re: [w3c/browser-payment-api] PaymentRequest constructor errors should be properly annotated (#290) Zach Koch
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) adamroach
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) ianbjacobs
• Re: [w3c/webpayments-methods-card] What if the card type is unknown by the payment app? (#19) Tommy Thorsen
• [w3c/webpayments-methods-card] What if the card type is unknown by the payment app? (#19) Tommy Thorsen

Last message date: Wednesday, 30 November 2016 23:55:29 UTC