- From: Joshua Zhao via GitHub <noreply@w3.org>
- Date: Tue, 19 Aug 2025 19:33:36 +0000
- To: public-webauthn@w3.org
> > as to facilitate experimentations with extensions of the protocol. > > You can fork Chromium (or Firefox or WebKit), make the change, compile, and then run your experiments. Then if they're successful, you can propose your extension in the working group for possible inclusion in the spec. > > While extensions are not required to be in the spec, the standards process has a higher chance of success w.r.t. being supported by mainstream clients. The custom-built browsers can only be installed on a limited number of users. This is only useful to validate the extension works, which isn't much in evaluating its successfulness. Unless we can experiment on a larger group of audience where client browser support is important, it's not sufficient to provide the necessary proof for its effectiveness unfortunately. Pass-through shouldn't be overly burdensome for browsers to implement. If we can implement it on a fork easily, it should be trivial for the vendors to do so too. I don't see a downside to adopt this behavior on browsers. -- GitHub Notification of comment by joshzhao Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1730#issuecomment-3201974823 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 August 2025 19:33:37 UTC