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

[w3c/browser-payment-api] "asynchronously perform the remaining steps" is not defined (#341)

[w3c/browser-payment-api] "contains a value for" isn't defined for dictionaries (#321)

[w3c/browser-payment-api] "store" value in [[internalSlot]] (#353)

[w3c/browser-payment-api] "valid decimal monetary value" should move to its own section (#303)

[w3c/browser-payment-api] A `PaymentItem` can't be a "valid decimal monetary value" (#334)

[w3c/browser-payment-api] A PaymentDetailsModifier may not have an additionalDisplayItems value present (#335)

[w3c/browser-payment-api] Add canMakeActivePayment() function to PaymentRequest object. (#310)

[w3c/browser-payment-api] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327)

[w3c/browser-payment-api] Ambiguous conformance requirement in constructor (#354)

[w3c/browser-payment-api] Behavior for multiple modifiers for the same payment method is not defined (#309)

[w3c/browser-payment-api] Browsing contexts don't have an "origin" (#324)

[w3c/browser-payment-api] chore: fix xrefs and dfns (#296)

[w3c/browser-payment-api] chore: xref internal slots (#319)

[w3c/browser-payment-api] Collect Privacy and Security considerations (#331)

[w3c/browser-payment-api] Combine scope and goal + relocate/reduce conformance (#294)

[w3c/browser-payment-api] currencySystem seems like a recipe for interop hell (#305)

[w3c/browser-payment-api] Data interfaces with serializers (#299)

[w3c/browser-payment-api] Detecting Payment Method Availability (#316)

[w3c/browser-payment-api] DOMExceptions are now in WebIDL 2 (#314)

[w3c/browser-payment-api] DOMStrings don't contain "characters" (#322)

[w3c/browser-payment-api] Dynamic Currency Conversion requirements (#289)

[w3c/browser-payment-api] editorial: clarify examples (#329)

[w3c/browser-payment-api] editorial: move monetary value to Definitions sec (closes #303) (#313)

[w3c/browser-payment-api] editorial: PaymentRequest ctor, describe error (closes #290) (#355)

[w3c/browser-payment-api] editorial: PaymentRequest ctor, describe errors (closes #290) (#355)

[w3c/browser-payment-api] enum PaymentComplete's "" (#308)

[w3c/browser-payment-api] Example update (#317)

[w3c/browser-payment-api] Examples in the spec (#274)

[w3c/browser-payment-api] Fix example (#318)

[w3c/browser-payment-api] Fix example add inco (#318)

[w3c/browser-payment-api] How are currency systems expected to be implemented in practice? (#343)

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

[w3c/browser-payment-api] Is it intended that abort() rejects the acceptPromise and resolves its return value in separate tasks? (#340)

[w3c/browser-payment-api] Is section 3.4 informative or normative? (#342)

[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)

[w3c/browser-payment-api] Making this API work with HTML Forms (#330)

[w3c/browser-payment-api] Merge pull request #1 from w3c/gh-pages (#315)

[w3c/browser-payment-api] normative(PaymentComplete): replace '' with 'unknown' (closes #308) (#312)

[w3c/browser-payment-api] PaymentAddress should be a dictionary (#299)

[w3c/browser-payment-api] PaymentDetails "total" member should be required (#320)

[w3c/browser-payment-api] PaymentDetails may not have values present for various sequences, but the PaymentRequest constructor assumes that it does (#333)

[w3c/browser-payment-api] PaymentOptions seems overly verbose (#326)

[w3c/browser-payment-api] PaymentOptions seems overly verbose/overlaps with HTML (#326)

[w3c/browser-payment-api] PaymentRequest constructor errors should be properly annotated (#290)

[w3c/browser-payment-api] PaymentRequest type checks (#306)

[w3c/browser-payment-api] PaymentRequest type checks (valid non-negative monetary value) (#306)

[w3c/browser-payment-api] PaymentResponse's details (#328)

[w3c/browser-payment-api] PaymentResponse's details could lead to problems (#328)

[w3c/browser-payment-api] Please define your internal slot notation before using it (#336)

[w3c/browser-payment-api] Relocate conformance section + markup fixes (#295)

[w3c/browser-payment-api] Response/Request semantics and cancellation (#298)

[w3c/browser-payment-api] Send HTMLIFrameElement.allowPaymentRequest to HTML spec (#311)

[w3c/browser-payment-api] Setting internal slots of objects from asynchronous steps is not OK (#339)

[w3c/browser-payment-api] Should PaymentDetails.total be marked as required in IDL? (#300)

[w3c/browser-payment-api] Should values for supportedNetworks be defined in Basic Card or separately? (#325)

[w3c/browser-payment-api] Shouldn't HTMLIFrameElement. allowPaymentRequest go into "sandbox"? (#311)

[w3c/browser-payment-api] style(abstract): simplify abstract (#293)

[w3c/browser-payment-api] Supporting push payment methods (#224)

[w3c/browser-payment-api] The "data" member of PaymentDetailsModifier doesn't seem to be used for anything (#346)

[w3c/browser-payment-api] The "data" member of PaymentMethodData doesn't seem to actually be used for anything (#338)

[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)

[w3c/browser-payment-api] The myth of JSON-serializable object (#307)

[w3c/browser-payment-api] The origin restrictions in the PaymentRequest are not nearly strong enough (#332)

[w3c/browser-payment-api] The shipping address/option changed algorithms should not be synchronously poking internal slots (#351)

[w3c/browser-payment-api] The shippingOptions field is used in more cases than the spec claims, as far as I can tell (#345)

[w3c/browser-payment-api] The target of a PaymentRequestUpdateEvent may not be a PaymentRequest object (#347)

[w3c/browser-payment-api] Tidy up document (#297)

[w3c/browser-payment-api] updateWith will silently ignore data in hard-to-debug ways (#350)

[w3c/browser-payment-api] valid decimal monetary value maybe overly restrictive (#304)

[w3c/browser-payment-api] What does it mean for a user agent to validate displayItems? (#344)

[w3c/browser-payment-api] What is "the script calling the constructor"? (#323)

[w3c/browser-payment-api] What is the shippingAddress of a PaymentResponse if requestShipping was false? (#352)

[w3c/browser-payment-api] What is the shippingAddress/shippingOption of a PaymentResponse if requestShipping was false? (#352)

[w3c/browser-payment-api] Why does PaymentRequest constructor throw on details.error (#302)

[w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301)

[w3c/browser-payment-api] Why is the "shippingType" member of PaymentOptions not a PaymentShippingType? (#337)

[w3c/webpayments-method-identifiers] SRI on manifest (#18)

[w3c/webpayments-method-identifiers] Support for PMI's with schemes other than https? (#17)

[w3c/webpayments-method-identifiers] Update of PMI spec (#16)

[w3c/webpayments-methods-card] Behavior when method-specific data is invalid (#20)

[w3c/webpayments-methods-card] What if the card type is unknown by the payment app? (#19)

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

[w3c/webpayments-payment-apps-api] Analyse security properties of payment app execution environment (#23)

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

[w3c/webpayments-payment-apps-api] Edited specification to remove notions of open/proprietary (#70)

[w3c/webpayments-payment-apps-api] How can a Browser-based Payment App cancel the payment flow? (#37)

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

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

[w3c/webpayments-payment-apps-api] Pass along a Transaction ID (#47)

[w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48)

[w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63)

[w3c/webpayments-payment-apps-api] Users MUST be able to prevent the display of unregistered payment apps (#59)

[w3c/webpayments-payment-apps-api] Versioning (#45)

[w3c/webpayments-payment-apps-api] What does "icon" mean? (#69)

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