public-webpayments-specs@w3.org from January 2019 by subject

[w3c/payment-handler] Add a privacy consideration note for issue #330. (#331)

[w3c/payment-handler] CanMakePaymentEvent handling algorithm unclear (#330)

[w3c/payment-handler] Rename canMakePayment* hasEnrolledInstrument (#332)

[w3c/payment-handler] updated per DHM (#329)

[w3c/payment-method-basic-card] Leave Off Unneeded Information (#5)

[w3c/payment-method-basic-card] Redact more things from billingAddress (#65)

[w3c/payment-method-basic-card] Removed deprecated shortname field (#66)

[w3c/payment-method-id] chore(w3c): small update to w3c json (#59)

[w3c/payment-method-id] Fix link to implementation report (#58)

[w3c/payment-method-id] Generate an implementation report (#54)

[w3c/payment-method-id] Json update (#59)

[w3c/payment-method-id] Prepare for Proposed Recommendation (#56)

[w3c/payment-request] Applying "Detached" JWS Signatures to PaymentRequest (#714)

[w3c/payment-request] Attach 'payment request is showing boolean' to top-level browsing context (#811)

[w3c/payment-request] Clarification question for `show()` algorithm (#820)

[w3c/payment-request] Clarify retry() when errorFields are not passed (#825)

[w3c/payment-request] Clarify when the user can abort the payment request algorithm (#796)

[w3c/payment-request] Clarify when the user can abort the payment request algorithm (#810)

[w3c/payment-request] Confirm tests and specs align (#779)

[w3c/payment-request] consider requiring an error (non-empty dict) for .retry()? (#792)

[w3c/payment-request] Define handling of multiple applicable modifiers (#684)

[w3c/payment-request] Define handling of multiple applicable modifiers (#824)

[w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698)

[w3c/payment-request] Do .data IDL conversion in constructor (#828)

[w3c/payment-request] Do .data IDL conversion in constructor (#829)

[w3c/payment-request] Editorial: relationship to Feature Policy spec (#822)

[w3c/payment-request] Editorial: reworded examples, nits (#827)

[w3c/payment-request] Extensibility of PaymentResponse.complete(result) (#817)

[w3c/payment-request] fix: close request if sheet is showing (#821)

[w3c/payment-request] fix: convert PaymentMethodData.data (#812)

[w3c/payment-request] Integrate with Feature Policy (#822)

[w3c/payment-request] Integration with Feature Policy (#600)

[w3c/payment-request] Modifiers (#828)

[w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753)

[w3c/payment-request] PaymentAddress 'region' inconsistencies (#663)

[w3c/payment-request] Providing an `AbortSignal` instead of calling .abort() (#757)

[w3c/payment-request] Remove PaymentAddress' regionCode attribute (#823)

[w3c/payment-request] Remove regionCode attribute (#823)

[w3c/payment-request] Remove regionCode attribute (doesn't spark joy) (#823)

[w3c/payment-request] Rethink "payment request is showing" boolean (#809)

[w3c/payment-request] Should we put `regionCode` attribute at risk? (#816)

[w3c/payment-request] Some clarifications with Payment Request API (#774)

[w3c/payment-request] Spec hasEnrolledInstrument (#830)

[w3c/payment-request] Support for language the form is served (#819)

[w3c/payment-request] test suite that checks whether shipping options can be updated (#791)

[w3c/payment-request] Updated per Dom Hazael-Massieux (#826)

Last message date: Thursday, 31 January 2019 17:51:50 UTC