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

[w3c/browser-payment-api] "allowed to use" check is incorrect (#363)

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

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

[w3c/browser-payment-api] Add `enableLegacyCheckout` option to PaymentOptions. (#365)

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

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

[w3c/browser-payment-api] Add canMakePayment() method (#380)

[w3c/browser-payment-api] Adding dialog close event (#387)

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

[w3c/browser-payment-api] Change "SHOULD NEVER" to "MUST NOT" (#356)

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

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

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

[w3c/browser-payment-api] Editorial: define and link to the different states (#376)

[w3c/browser-payment-api] Editorial: don't capitalize RFC 2119 terms (#377)

[w3c/browser-payment-api] Editorial: introductory explanations of methods should be non-normative notes (#379)

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

[w3c/browser-payment-api] Editorial: refer to methods with parentheses for clarity, and spell out their params in their definition (#378)

[w3c/browser-payment-api] Editorial: use new language for DOMExceptions (#375)

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

[w3c/browser-payment-api] Explicitly state any cases where an iframe with an allowpaymentrequest attribute is not allowed to make payment requests (#358)

[w3c/browser-payment-api] Explicitly state any cases where an iframe with an allowpaymentrequest is not allowed to make payment requests (#358)

[w3c/browser-payment-api] fix: don't validate display items (closes #344) (#357)

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

[w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291)

[w3c/browser-payment-api] In parallel (#369)

[w3c/browser-payment-api] Introduce paymenRequestID (#292)

[w3c/browser-payment-api] Invoke "allowed to use" always (#383)

[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] Minor typographical fixes (#368)

[w3c/browser-payment-api] Need to define the interaction of payment API with navigation and browsing context destruction (#360)

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

[w3c/browser-payment-api] PaymentApp fails to abort payment flow (#384)

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

[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 constructor validation ordering does not match Blink at all (#373)

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

[w3c/browser-payment-api] Reference HTML for allowpaymentrequest definition (#359)

[w3c/browser-payment-api] Reference W3C HTML for allowpaymentrequest definition (#359)

[w3c/browser-payment-api] ReSpec error viewing the spec (#386)

[w3c/browser-payment-api] Security hole in payment API when a constructor from a no longer active document is invoked (#361)

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

[w3c/browser-payment-api] Serializer behavior (#385)

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

[w3c/browser-payment-api] Straighten out the payment method data flow (#382)

[w3c/browser-payment-api] Switch internal slot notation to ., not @ (#370)

[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 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] There is no concept of "called from" some browsing context (#362)

[w3c/browser-payment-api] Update allowed to use check. (#364)

[w3c/browser-payment-api] Update allowed to use check. (#364) (2893862)

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

[w3c/browser-payment-api] Use current settings object. (#366)

[w3c/browser-payment-api] Validate payment method data (#381)

[w3c/browser-payment-api] Various fixes to the PaymentRequest constructor (#374)

[w3c/browser-payment-api] Various fixes to updateWith (#372)

[w3c/browser-payment-api] waitForUpdate is not defined (#371)

[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 mechanism for limiting repeated calls to canMakePayments ? (#367)

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

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

[w3c/webpayments-method-identifiers] How should we address payment method manifest files? (#19)

[w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11)

[w3c/webpayments-method-identifiers] Schema.org PaymentMethod as namespace for short strings (#13)

[w3c/webpayments-method-identifiers] Should a payment method identifier (URL) resolve to a machine readable resource that describes it? (#3)

[w3c/webpayments-method-identifiers] Should a payment method identifier that is a URL bind that payment method to a single payment app or origin? (#12)

[w3c/webpayments-method-identifiers] Should we define nesting/grouping semantics for payment method identifier matching? (#1)

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

[w3c/webpayments-methods-card] Add validate payment method data algorithm (#21)

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

[w3c/webpayments-methods-card] Update spec to use 4-digit expirations (#22)

[w3c/webpayments-payment-apps-api] (Deleted this edit by mistake before merged) (#78)

[w3c/webpayments-payment-apps-api] added link to issue 73 (#75)

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

[w3c/webpayments-payment-apps-api] Lambda functions for app matching (#76)

[w3c/webpayments-payment-apps-api] Need to specify behavior for Clients.openWindow (#73)

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

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

[w3c/webpayments-payment-apps-api] Should payment instrument details be included at registration? (#12)

[w3c/webpayments-payment-apps-api] Suggested apps (#74)

[w3c/webpayments-payment-apps-api] Updated intro on display of apps and openWindow (#77)

Last message date: Wednesday, 28 December 2016 23:05:09 UTC