ianbjacobs
ianbjacobs
We added payeeName to the specification; we'll want to be able to localize that value as well.
@aphillips, @r12a, @xfq, we've not heard much news about generalized support for localizable strings in ECMAScript or in a "standalone spec" that could be referenced from SPC, WebAuthn, and other...
@aphillips, @r12a, @xfq, it would be great to hear from you. Could we discuss no later than TPAC? Thanks!
Closing this issue based on more recent and more specific I18N issues #205 and and #209, as well as discussion with @aphillips during TPAC. For a more recent I18N checklist,...
@Goosth, I haven't checked in lately to see whether we've addressed issues here to your satisfaction.
See FIDO white paper related to multi-device credentials: https://fidoalliance.org/white-paper-multi-device-fido-credentials/
Based on discussion about: https://github.com/w3c/secure-payment-confirmation/pull/183#discussion_r861788122 For future discussion: SPC talks about "the current device." Based on CABLE and synched credentials we may wish to revisit that phrase in the specification...
@danyao, If I've understood, there are two user gestures involved: 1) Enrollment: The user consents to the creation of the CryptoKeyCredential. 2) Transaction: The CryptoKeyCredential is only made available to...
Based on further conversation, adding a remark here: if there are any options in the user experience, this raises the question of prioritization of concerns. My initial recommendation would be:...
@Goosth, interesting point. "More security wins" could be an interesting principle. (I need to think more about it. "Security" may be the wrong word here, although I hope it's the...