- From: Thomas Cannon via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Feb 2025 23:00:44 +0000
- To: public-webauthn@w3.org
> This suggestion might have been actionable when the WebAuthn work was starting in February 2016 or when FIDO 2 was being chartered in October 2014 but this suggestion wasn't even made until July 2019 - months after the Level 1 spec was already final. If you're arguing for a single-path approach, this reads as an indictment of the Level 1 spec and its lack of understanding in how the browser operates. Also; love to be a community member implicitly held at fault as being tardy; for not coming up with an idea as an outside contributor to a spec that became popular as people realized its importance and actively want to adopt it in their projects while still being good developers who understand the problems of web development. There are approaches that could essentially encapsulate the JS behavior into a declarative element; my pet favorite idea is: https://github.com/w3c/webauthn/issues/1255#issuecomment-560169100 But even if that one doesn't fully pan out, we can propose _something_. I fully recognize how difficult it is, and I'm very grateful for all the work that's been done. But unless there's guidance on what the solution might even look like, we're never going to get anywhere with it. It'll always be DOA. It doesn't have to be perfect, it'll obviously change. flexbox did, CSS grid did. But I think the working group needs to come forward with some sort of shape of the API, so we can, as a community, help flesh it out and tackle this problem. > That didn’t stop the standardization of declarative popover, declarative shadow DOM, lazy loaded images, the dialog element, the inert attribute… @Kerrick has a great point here, we have numerous examples of "multiple ways to solve a problem." People choose the version that ships with the browser (even if it might not be ideal) because it's there "natively" and that's the tradeoff they're willing to make. > The way I see it is that if WebAuthn is already getting burdened by legacy issues this early, then something may have gone very wrong. Exactly this. -- GitHub Notification of comment by tcannonfodder Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1255#issuecomment-2669954607 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 February 2025 23:00:45 UTC