- From: John Bradley via GitHub <sysbot+gh@w3.org>
- Date: Sun, 11 Jun 2023 19:19:42 +0000
- To: public-webauthn@w3.org
Are browsers really going to set this flag to false if they have a platform authenticator and support Hybrid but some setting in the OS is stopping hybrid from being used? I don't think I got that. That is an interesting question, I guess on Windows this could happen but I think platform support for Hybrid is coming in the next several months so it may be a short term problem on Windows. On MacOS there is platform support for Hybrid that will get around the problem if Goole uses it. @MasterKale it seems like your use case is for and ideintier first flow where you know what transports are set on the available credentialID. In that case, are you looking for the available transports as what you really want? Without an identifier first flow the RP should probably just do conditional mediation and let the OS sort it out. This sort of flag seems mostly useful in the case where the RP is doing identifier first with an allow list? If the browser is going to say I support hybrid, or some combination of hybrid and platform is it still useful to you if the browser doesn't return no in the case BLE is disabled? -- GitHub Notification of comment by ve7jtb Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1901#issuecomment-1586304797 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 11 June 2023 19:19:43 UTC