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

adamroach

• Re: [w3c/browser-payment-api] "asynchronously perform the remaining steps" is not defined (#341) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] The "data" member of PaymentMethodData doesn't seem to actually be used for anything (#338) (Wednesday, 30 November)
• Re: [w3c/webpayments-payment-apps-api] (Promise<PaymentResponse> or PaymentResponse) is invalid Web IDL. (#71) (Tuesday, 22 November)
• Re: [w3c/browser-payment-api] Example update (#317) (Friday, 18 November)
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Tuesday, 1 November)

Ade Bateman

• Re: [w3c/browser-payment-api] editorial: PaymentRequest ctor, describe errors (closes #290) (#355) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] editorial: clarify examples (#329) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] PaymentDetails "total" member should be required (#320) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) (Tuesday, 29 November)
• Re: [w3c/browser-payment-api] PaymentDetails "total" member should be required (#320) (Tuesday, 29 November)
• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) (Tuesday, 29 November)
• Re: [w3c/browser-payment-api] chore: xref internal slots (#319) (Tuesday, 29 November)
• Re: [w3c/browser-payment-api] Fix example (#318) (Tuesday, 29 November)
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] editorial: move monetary value to Definitions sec (closes #303) (#313) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] "valid decimal monetary value" should move to its own section (#303) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] editorial: move monetary value to Definitions sec (closes #303) (#313) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] normative(PaymentComplete): replace '' with 'unknown' (closes #308) (#312) (Thursday, 17 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] Response/Request semantics and cancellation (#298) (Tuesday, 15 November)
• Re: [w3c/browser-payment-api] Tidy up document (#297) (Tuesday, 15 November)
• Re: [w3c/browser-payment-api] chore: fix xrefs and dfns (#296) (Tuesday, 15 November)
• Re: [w3c/browser-payment-api] Relocate conformance section + markup fixes (#295) (Tuesday, 15 November)
• Re: [w3c/browser-payment-api] style(abstract): simplify abstract (#293) (Tuesday, 15 November)
• Re: [w3c/browser-payment-api] style(abstract): simplify abstract (#293) (Tuesday, 15 November)

Adrian Hope-Bailie

• Re: [w3c/webpayments-payment-apps-api] Modify section 10.4 Payment App Response to allow an app to cancel. (#72) (Sunday, 27 November)
• Re: [w3c/webpayments-payment-apps-api] Modify section 10.4 Payment App Response to allow an app to cancel. (#72) (Friday, 25 November)
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) (Friday, 25 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Wednesday, 23 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Tuesday, 22 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Monday, 21 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Sunday, 20 November)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Sunday, 20 November)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Sunday, 20 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Sunday, 20 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Friday, 18 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Friday, 18 November)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 18 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Friday, 18 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Friday, 18 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Friday, 18 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Friday, 18 November)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 18 November)
• [w3c/webpayments-method-identifiers] SRI on manifest (#18) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) (Thursday, 17 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Thursday, 17 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Thursday, 17 November)
• [w3c/webpayments-method-identifiers] Support for PMI's with schemes other than https? (#17) (Thursday, 17 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Thursday, 17 November)
• Re: [w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70) (Thursday, 17 November)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Thursday, 17 November)
• Re: [w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70) (Thursday, 17 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] "valid decimal monetary value" should move to its own section (#303) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) (Monday, 14 November)
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Monday, 14 November)
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) (Monday, 14 November)
• Re: [w3c/browser-payment-api] style(abstract): simplify abstract (#293) (Thursday, 10 November)
• Re: [w3c/webpayments-payment-apps-api] Display order edits (#68) (Monday, 7 November)
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Tuesday, 1 November)

Anne van Kesteren

• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) (Wednesday, 23 November)
• Re: [w3c/browser-payment-api] Shouldn't HTMLIFrameElement. allowPaymentRequest go into "sandbox"? (#311) (Wednesday, 16 November)

Boris Zbarsky

• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] Is section 3.4 informative or normative? (#342) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] What is the shippingAddress/shippingOption of a PaymentResponse if requestShipping was false? (#352) (Wednesday, 30 November)
• [w3c/browser-payment-api] What is the shippingAddress of a PaymentResponse if requestShipping was false? (#352) (Wednesday, 30 November)
• [w3c/browser-payment-api] The shipping address/option changed algorithms should not be synchronously poking internal slots (#351) (Wednesday, 30 November)
• [w3c/browser-payment-api] updateWith will silently ignore data in hard-to-debug ways (#350) (Wednesday, 30 November)
• [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) (Wednesday, 30 November)
• [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) (Wednesday, 30 November)
• [w3c/browser-payment-api] The target of a PaymentRequestUpdateEvent may not be a PaymentRequest object (#347) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] What does it mean for a user agent to validate displayItems? (#344) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] "asynchronously perform the remaining steps" is not defined (#341) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] The "data" member of PaymentMethodData doesn't seem to actually be used for anything (#338) (Wednesday, 30 November)
• [w3c/browser-payment-api] The "data" member of PaymentDetailsModifier doesn't seem to be used for anything (#346) (Wednesday, 30 November)
• [w3c/browser-payment-api] The shippingOptions field is used in more cases than the spec claims, as far as I can tell (#345) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] How are currency systems expected to be implemented in practice? (#343) (Wednesday, 30 November)
• [w3c/browser-payment-api] What does it mean for a user agent to validate displayItems? (#344) (Wednesday, 30 November)
• [w3c/browser-payment-api] How are currency systems expected to be implemented in practice? (#343) (Wednesday, 30 November)
• [w3c/browser-payment-api] Is section 3.4 informative or normative? (#342) (Wednesday, 30 November)
• [w3c/browser-payment-api] "asynchronously perform the remaining steps" is not defined (#341) (Wednesday, 30 November)
• [w3c/browser-payment-api] Is it intended that abort() rejects the acceptPromise and resolves its return value in separate tasks? (#340) (Wednesday, 30 November)
• [w3c/browser-payment-api] Setting internal slots of objects from asynchronous steps is not OK (#339) (Wednesday, 30 November)
• [w3c/browser-payment-api] The "data" member of PaymentMethodData doesn't seem to actually be used for anything (#338) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] Please define your internal slot notation before using it (#336) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] PaymentDetails may not have values present for various sequences, but the PaymentRequest constructor assumes that it does (#333) (Wednesday, 30 November)
• [w3c/browser-payment-api] Why is the "shippingType" member of PaymentOptions not a PaymentShippingType? (#337) (Wednesday, 30 November)
• [w3c/browser-payment-api] Please define your internal slot notation before using it (#336) (Wednesday, 30 November)
• [w3c/browser-payment-api] A PaymentDetailsModifier may not have an additionalDisplayItems value present (#335) (Wednesday, 30 November)
• [w3c/browser-payment-api] A `PaymentItem` can't be a "valid decimal monetary value" (#334) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] "contains a value for" isn't defined for dictionaries (#321) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] PaymentDetails may not have values present for various sequences, but the PaymentRequest constructor assumes that it does (#333) (Wednesday, 30 November)
• [w3c/browser-payment-api] PaymentDetails may not have values present for various sequences, but the PaymentRequest constructor assumes that it does (#333) (Wednesday, 30 November)
• [w3c/browser-payment-api] The origin restrictions in the PaymentRequest are not nearly strong enough (#332) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] PaymentDetails "total" member should be required (#320) (Wednesday, 30 November)
• [w3c/browser-payment-api] Browsing contexts don't have an "origin" (#324) (Monday, 21 November)
• [w3c/browser-payment-api] What is "the script calling the constructor"? (#323) (Monday, 21 November)
• [w3c/browser-payment-api] DOMStrings don't contain "characters" (#322) (Monday, 21 November)
• [w3c/browser-payment-api] "contains a value for" isn't defined for dictionaries (#321) (Monday, 21 November)
• [w3c/browser-payment-api] PaymentDetails "total" member should be required (#320) (Monday, 21 November)

Dave Longley

• Re: [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) (Thursday, 17 November)

Elliott Sprehn

• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Tuesday, 22 November)

Ian Clelland

• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Sunday, 20 November)

ianbjacobs

• Re: [w3c/browser-payment-api] Supporting push payment methods (#224) (Wednesday, 30 November)
• Re: [w3c/webpayments-payment-apps-api] Analyse security properties of payment app execution environment (#23) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] What does it mean for a user agent to validate displayItems? (#344) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) (Tuesday, 29 November)
• Re: [w3c/webpayments-payment-apps-api] What does "icon" mean? (#69) (Tuesday, 29 November)
• Re: [w3c/webpayments-payment-apps-api] (Promise<PaymentResponse> or PaymentResponse) is invalid Web IDL. (#71) (Tuesday, 29 November)
• Re: [w3c/browser-payment-api] Collect Privacy and Security considerations (#331) (Monday, 28 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Monday, 28 November)
• Re: [w3c/webpayments-payment-apps-api] Modify section 10.4 Payment App Response to allow an app to cancel. (#72) (Friday, 25 November)
• Re: [w3c/webpayments-payment-apps-api] What does "icon" mean? (#69) (Wednesday, 23 November)
• Re: [w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70) (Wednesday, 23 November)
• Re: [w3c/webpayments-payment-apps-api] How can a Browser-based Payment App cancel the payment flow? (#37) (Wednesday, 23 November)
• Re: [w3c/webpayments-payment-apps-api] What does "icon" mean? (#69) (Wednesday, 23 November)
• Re: [w3c/webpayments-payment-apps-api] (Promise<PaymentResponse> or PaymentResponse) is invalid Web IDL. (#71) (Tuesday, 22 November)
• [w3c/browser-payment-api] Should values for supportedNetworks be defined in Basic Card or separately? (#325) (Tuesday, 22 November)
• Re: [w3c/webpayments-payment-apps-api] (Promise<PaymentResponse> or PaymentResponse) is invalid Web IDL. (#71) (Tuesday, 22 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Monday, 21 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Friday, 18 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Friday, 18 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Friday, 18 November)
• Re: [w3c/browser-payment-api] Fix example add inco (#318) (Friday, 18 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Thursday, 17 November)
• [w3c/browser-payment-api] Example update (#317) (Thursday, 17 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Thursday, 17 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Thursday, 17 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Thursday, 17 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Thursday, 17 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Thursday, 17 November)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Thursday, 17 November)
• Re: [w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70) (Thursday, 17 November)
• Re: [w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70) (Thursday, 17 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Thursday, 17 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Thursday, 17 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Thursday, 17 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Thursday, 17 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Behavior for multiple modifiers for the same payment method is not defined (#309) (Wednesday, 16 November)
• Re: [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Wednesday, 16 November)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Wednesday, 16 November)
• Re: [w3c/webpayments-payment-apps-api] Versioning (#45) (Wednesday, 16 November)
• Re: [w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70) (Wednesday, 16 November)
• Re: [w3c/webpayments-payment-apps-api] Pass along a Transaction ID (#47) (Wednesday, 16 November)
• Re: [w3c/webpayments-payment-apps-api] Users MUST be able to prevent the display of unregistered payment apps (#59) (Wednesday, 16 November)
• Re: [w3c/webpayments-payment-apps-api] Users MUST be able to prevent the display of unregistered payment apps (#59) (Wednesday, 16 November)
• Re: [w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70) (Wednesday, 16 November)
• Re: [w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63) (Wednesday, 16 November)
• Re: [w3c/webpayments-payment-apps-api] No definition of Open and Proprietary payment methods (#67) (Wednesday, 16 November)
• Re: [w3c/webpayments-payment-apps-api] No definition of Open and Proprietary payment methods (#67) (Wednesday, 16 November)
• [w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70) (Wednesday, 16 November)
• [w3c/webpayments-method-identifiers] Update of PMI spec (#16) (Wednesday, 16 November)
• [w3c/webpayments-payment-apps-api] What does "icon" mean? (#69) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] Should PaymentDetails.total be marked as required in IDL? (#300) (Wednesday, 16 November)
• Re: [w3c/webpayments-payment-apps-api] Display order edits (#68) (Tuesday, 15 November)
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) (Tuesday, 15 November)
• [w3c/webpayments-payment-apps-api] Display order edits (#68) (Sunday, 6 November)
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Tuesday, 1 November)

Ilya Grigorik

• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Wednesday, 23 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Friday, 18 November)

Jake Archibald

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

Jeff Burdges

• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) (Friday, 25 November)
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) (Tuesday, 15 November)

Jenan Wise

• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)

Jinho Bang

• [w3c/webpayments-payment-apps-api] (Promise<PaymentResponse> or PaymentResponse) is invalid Web IDL. (#71) (Monday, 21 November)

Mahesh Kulkarni

• [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Merge pull request #1 from w3c/gh-pages (#315) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] Merge pull request #1 from w3c/gh-pages (#315) (Wednesday, 16 November)
• [w3c/browser-payment-api] Merge pull request #1 from w3c/gh-pages (#315) (Wednesday, 16 November)

Marcos Cáceres

• [w3c/browser-payment-api] editorial: PaymentRequest ctor, describe error (closes #290) (#355) (Wednesday, 30 November)
• [w3c/browser-payment-api] Ambiguous conformance requirement in constructor (#354) (Wednesday, 30 November)
• [w3c/browser-payment-api] "store" value in [[internalSlot]] (#353) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Wednesday, 30 November)
• Re: [w3c/webpayments-payment-apps-api] What does "icon" mean? (#69) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] Is section 3.4 informative or normative? (#342) (Wednesday, 30 November)
• 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) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] editorial: clarify examples (#329) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] How are currency systems expected to be implemented in practice? (#343) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Monday, 28 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Monday, 28 November)
• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) (Monday, 28 November)
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) (Monday, 28 November)
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) (Friday, 25 November)
• Re: [w3c/browser-payment-api] Making this API work with HTML Forms (#330) (Thursday, 24 November)
• [w3c/browser-payment-api] Collect Privacy and Security considerations (#331) (Thursday, 24 November)
• Re: [w3c/browser-payment-api] Examples in the spec (#274) (Thursday, 24 November)
• Re: [w3c/browser-payment-api] Making this API work with HTML Forms (#330) (Thursday, 24 November)
• [w3c/browser-payment-api] Making this API work with HTML Forms (#330) (Thursday, 24 November)
• [w3c/browser-payment-api] editorial: clarify examples (#329) (Thursday, 24 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Thursday, 24 November)
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) (Thursday, 24 November)
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) (Thursday, 24 November)
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) (Thursday, 24 November)
• Re: [w3c/browser-payment-api] PaymentResponse's details could lead to problems (#328) (Wednesday, 23 November)
• Re: [w3c/browser-payment-api] PaymentResponse's details could lead to problems (#328) (Wednesday, 23 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Wednesday, 23 November)
• [w3c/browser-payment-api] PaymentResponse's details (#328) (Wednesday, 23 November)
• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) (Wednesday, 23 November)
• Re: [w3c/browser-payment-api] PaymentAddress should be a dictionary (#299) (Wednesday, 23 November)
• Re: [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) (Wednesday, 23 November)
• [w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) (Wednesday, 23 November)
• [w3c/browser-payment-api] PaymentOptions seems overly verbose (#326) (Wednesday, 23 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Wednesday, 23 November)
• Re: [w3c/browser-payment-api] DOMExceptions are now in WebIDL 2 (#314) (Monday, 21 November)
• [w3c/browser-payment-api] chore: xref internal slots (#319) (Monday, 21 November)
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) (Monday, 21 November)
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) (Monday, 21 November)
• Re: [w3c/browser-payment-api] enum PaymentComplete's "" (#308) (Monday, 21 November)
• Re: [w3c/browser-payment-api] normative(PaymentComplete): replace '' with 'unknown' (closes #308) (#312) (Monday, 21 November)
• Re: [w3c/browser-payment-api] Fix example (#318) (Friday, 18 November)
• Re: [w3c/browser-payment-api] Fix example (#318) (Friday, 18 November)
• [w3c/browser-payment-api] Fix example add inco (#318) (Friday, 18 November)
• Re: [w3c/browser-payment-api] Example update (#317) (Friday, 18 November)
• Re: [w3c/browser-payment-api] Example update (#317) (Friday, 18 November)
• Re: [w3c/browser-payment-api] Example update (#317) (Friday, 18 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Friday, 18 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Friday, 18 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Friday, 18 November)
• Re: [w3c/browser-payment-api] Example update (#317) (Friday, 18 November)
• Re: [w3c/browser-payment-api] Example update (#317) (Friday, 18 November)
• Re: [w3c/browser-payment-api] normative(PaymentComplete): replace '' with 'unknown' (closes #308) (#312) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Shouldn't HTMLIFrameElement. allowPaymentRequest go into "sandbox"? (#311) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] editorial: move monetary value to Definitions sec (closes #303) (#313) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] editorial: move monetary value to Definitions sec (closes #303) (#313) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] "valid decimal monetary value" should move to its own section (#303) (Wednesday, 16 November)
• [w3c/browser-payment-api] DOMExceptions are now in WebIDL 2 (#314) (Wednesday, 16 November)
• [w3c/browser-payment-api] editorial: move monetary value to Definitions sec (closes #303) (#313) (Wednesday, 16 November)
• [w3c/browser-payment-api] normative(PaymentComplete): replace '' with 'unknown' (closes #308) (#312) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) (Wednesday, 16 November)
• [w3c/browser-payment-api] Shouldn't HTMLIFrameElement. allowPaymentRequest go into "sandbox"? (#311) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] Tidy up document (#297) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] chore: fix xrefs and dfns (#296) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] Relocate conformance section + markup fixes (#295) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] Combine scope and goal + relocate/reduce conformance (#294) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] Should PaymentDetails.total be marked as required in IDL? (#300) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] Should PaymentDetails.total be marked as required in IDL? (#300) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] Relocate conformance section + markup fixes (#295) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] Combine scope and goal + relocate/reduce conformance (#294) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] Tidy up document (#297) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] Should PaymentDetails.total be marked as required in IDL? (#300) (Tuesday, 15 November)
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) (Tuesday, 15 November)
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) (Tuesday, 15 November)
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) (Tuesday, 15 November)
• Re: [w3c/browser-payment-api] Response/Request semantics and cancellation (#298) (Monday, 14 November)
• [w3c/browser-payment-api] enum PaymentComplete's "" (#308) (Monday, 14 November)
• [w3c/browser-payment-api] The myth of JSON-serializable object (#307) (Monday, 14 November)
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) (Monday, 14 November)
• Re: [w3c/browser-payment-api] PaymentRequest type checks (valid non-negative monetary value) (#306) (Monday, 14 November)
• [w3c/browser-payment-api] PaymentRequest type checks (#306) (Monday, 14 November)
• [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) (Monday, 14 November)
• [w3c/browser-payment-api] valid decimal monetary value maybe overly restrictive (#304) (Monday, 14 November)
• [w3c/browser-payment-api] "valid decimal monetary value" should move to its own section (#303) (Monday, 14 November)
• [w3c/browser-payment-api] Why does PaymentRequest constructor throw on details.error (#302) (Monday, 14 November)
• [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) (Monday, 14 November)
• [w3c/browser-payment-api] Should PaymentDetails.total be marked as required in IDL? (#300) (Monday, 14 November)
• [w3c/browser-payment-api] Data interfaces with serializers (#299) (Monday, 14 November)
• [w3c/browser-payment-api] Response/Request semantics and cancellation (#298) (Monday, 14 November)
• Re: [w3c/browser-payment-api] PaymentRequest constructor errors should be properly annotated (#290) (Monday, 14 November)
• Re: [w3c/browser-payment-api] Dynamic Currency Conversion requirements (#289) (Monday, 14 November)
• Re: [w3c/browser-payment-api] Dynamic Currency Conversion requirements (#289) (Monday, 14 November)
• Re: [w3c/browser-payment-api] PaymentRequest constructor errors should be properly annotated (#290) (Monday, 14 November)
• Re: [w3c/browser-payment-api] Tidy up document (#297) (Monday, 14 November)
• [w3c/browser-payment-api] Tidy up document (#297) (Friday, 11 November)
• [w3c/browser-payment-api] chore: fix xrefs and dfns (#296) (Friday, 11 November)
• Re: [w3c/browser-payment-api] style(abstract): simplify abstract (#293) (Friday, 11 November)
• Re: [w3c/browser-payment-api] Relocate conformance section + markup fixes (#295) (Thursday, 10 November)
• Re: [w3c/browser-payment-api] Relocate conformance section + markup fixes (#295) (Thursday, 10 November)
• [w3c/browser-payment-api] Relocate conformance section + markup fixes (#295) (Thursday, 10 November)
• [w3c/browser-payment-api] Combine scope and goal + relocate/reduce conformance (#294) (Thursday, 10 November)
• [w3c/browser-payment-api] style(abstract): simplify abstract (#293) (Thursday, 10 November)

Marijn Kruisselbrink

• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)

maxpassion

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

Michael[tm] Smith

• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) (Monday, 28 November)
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) (Saturday, 26 November)
• Re: [w3c/browser-payment-api] editorial: move monetary value to Definitions sec (closes #303) (#313) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] editorial: move monetary value to Definitions sec (closes #303) (#313) (Wednesday, 16 November)

Mike West

• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Thursday, 17 November)

Nick Shearer

• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) (Saturday, 26 November)
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) (Friday, 25 November)
• Re: [w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326) (Thursday, 24 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• [w3c/browser-payment-api] Behavior for multiple modifiers for the same payment method is not defined (#309) (Monday, 14 November)
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Sunday, 13 November)

ojan

• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Wednesday, 30 November)

Philip Jägenstedt

• Re: [w3c/browser-payment-api] PaymentDetails "total" member should be required (#320) (Tuesday, 29 November)
• Re: [w3c/browser-payment-api] PaymentDetails "total" member should be required (#320) (Tuesday, 29 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Wednesday, 23 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Wednesday, 23 November)
• Re: [w3c/browser-payment-api] Shouldn't HTMLIFrameElement. allowPaymentRequest go into "sandbox"? (#311) (Wednesday, 16 November)

raymeskhoury

• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Tuesday, 22 November)

Rick Byers

• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) (Wednesday, 30 November)

Rouslan Solomakhin

• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Tuesday, 29 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Tuesday, 29 November)
• Re: [w3c/browser-payment-api] Making this API work with HTML Forms (#330) (Thursday, 24 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Wednesday, 23 November)
• Re: [w3c/webpayments-payment-apps-api] How can a Browser-based Payment App cancel the payment flow? (#37) (Wednesday, 23 November)
• [w3c/webpayments-methods-card] Behavior when method-specific data is invalid (#20) (Wednesday, 23 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Wednesday, 23 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Sunday, 20 November)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Sunday, 20 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Sunday, 20 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Friday, 18 November)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 18 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Friday, 18 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] normative(PaymentComplete): replace '' with 'unknown' (closes #308) (#312) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] The myth of JSON-serializable object (#307) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] Shouldn't HTMLIFrameElement. allowPaymentRequest go into "sandbox"? (#311) (Wednesday, 16 November)
• Re: [w3c/browser-payment-api] Behavior for multiple modifiers for the same payment method is not defined (#309) (Wednesday, 16 November)
• [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) (Tuesday, 15 November)

rvm4

• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Thursday, 3 November)
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Thursday, 3 November)
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Thursday, 3 November)

Shane McCarron

• Re: [w3c/browser-payment-api] chore: xref internal slots (#319) (Monday, 21 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Thursday, 17 November)
• Re: [w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310) (Tuesday, 15 November)
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Monday, 14 November)
• Re: [w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305) (Monday, 14 November)
• Re: [w3c/browser-payment-api] PaymentRequest type checks (valid non-negative monetary value) (#306) (Monday, 14 November)
• Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301) (Monday, 14 November)
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Monday, 14 November)
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Monday, 14 November)

stan-stripe

• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Monday, 14 November)
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Thursday, 10 November)

Tommy Thorsen

• Re: [w3c/webpayments-payment-apps-api] How can a Browser-based Payment App cancel the payment flow? (#37) (Friday, 25 November)
• Re: [w3c/webpayments-payment-apps-api] Modify section 10.4 Payment App Response to allow an app to cancel. (#72) (Friday, 25 November)
• Re: [w3c/webpayments-payment-apps-api] Modify section 10.4 Payment App Response to allow an app to cancel. (#72) (Friday, 25 November)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 25 November)
• Re: [w3c/webpayments-payment-apps-api] Modify section 10.4 Payment App Response to allow an app to cancel. (#72) (Friday, 25 November)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 25 November)
• Re: [w3c/webpayments-payment-apps-api] How can a Browser-based Payment App cancel the payment flow? (#37) (Thursday, 24 November)
• [w3c/webpayments-payment-apps-api] Modify section 10.4 Payment App Response to allow an app to cancel. (#72) (Thursday, 24 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Wednesday, 23 November)
• Re: [w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311) (Monday, 21 November)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 18 November)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 18 November)
• Re: [w3c/browser-payment-api] Behavior for multiple modifiers for the same payment method is not defined (#309) (Wednesday, 16 November)
• Re: [w3c/webpayments-methods-card] What if the card type is unknown by the payment app? (#19) (Tuesday, 1 November)
• [w3c/webpayments-methods-card] What if the card type is unknown by the payment app? (#19) (Tuesday, 1 November)

Zach Koch

• Re: [w3c/browser-payment-api] Making this API work with HTML Forms (#330) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] editorial: PaymentRequest ctor, describe errors (closes #290) (#355) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] normative(PaymentComplete): replace '' with 'unknown' (closes #308) (#312) (Wednesday, 30 November)
• Re: [w3c/browser-payment-api] PaymentRequest constructor errors should be properly annotated (#290) (Tuesday, 1 November)

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