- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Mon, 4 Apr 2022 19:46:05 +0200
- To: public-webauthn-adoption@w3.org
Hi, Here are the notes I took during our call today; next meeting on Apr 18th, to be chaired by Nick. * passkeys dev journey: still in progress * authenticator: good in formalizing spec; needs WG review & approval * conformance test suite: FIDO test suite planned for opening up - Paul will keep this group informed as more specific plans emerge * on-line course: on going work on making specific roadmap & timeline for new modules and runs * Chrome 100 came with CaBLE added webauthn enable registration via QR code https://twitter.com/IAmKale/status/1510303402412036098 ⇒ impact on RPs? RPs can't block it at registration when picking "cross-platform", even though that change impacts UX how could RPs better track these upcoming changes that may affect their flows? Tim: what threshold of UX change requires RPs attention? Matt: very low threshold given criticality how that UX in user flow may be something worth for FIDO alliance to invest resources in David: FIDO has been tracking feature support, but not UX changes so far tracking L3 features is generating a lot of interest Tim: no good place to track implementation behaviors; we thought our github org for passkeys may be a place to track these as issues Dom: could use Chromium localization files with WebAuthn strings to track these changes Tim: that said, devs at large RPs should run canary/beta Matt: definitely a lesson I need to take back internally Next meeting: * Apr 18 * WebAuthn WG meeting F2F on June 9 during RSA conference; WebAuthn Adoption CG participants can join (with WG chairs approval) Dom
Received on Monday, 4 April 2022 17:46:09 UTC