- From: Jeffrey Walton via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Jan 2025 06:10:34 +0000
- To: public-webauthn@w3.org
> From the WG call today: the biggest challenge right now is identifying a large enough number of users who would be positively impacted by the addition of non-JS support for passkey authentication to justify hypothetical implementation by browser vendors. Those of us who cross-participate in the FIDO Alliance can take this up with potentially interested WG's over there to see if there's been any communicated at-scale desire for this capability. Based on search results, it looks like between 1% and 3% of users do not have JavaScript enabled. That includes users who make the choice by installing browser extensions like NoScript; and corporate users who experience a policy that disables JavaScript. The 3% is an important threshold, in my opinion. That's the critical mass to support a feature. For example, in the US, the IRS would support a browser with 3% market share. It was a big deal back in the 1990's. I don't know what the IRS policy is nowadays (but its probably a lesser concern since the browser consolidations and evolution that have organically happened over time). Also see discussions like <https://www.mediawiki.org/wiki/No-JavaScript_notes>. And there will be folks who won't comment on this report because they don't want a GitHub account due to Microsoft. There's at least one on debian-users mailing list. -- GitHub Notification of comment by noloader Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1255#issuecomment-2608943185 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 23 January 2025 06:10:35 UTC