1Password extension breaks Bitwarden passkey support

Hi,

I'm currently using both Bitwarden and 1Password in Firefox for various reasons. I have passkeys disabled in the 1Password Firefox extension settings, and this setup used to work quite well for the past year or so.

However, recently something must have changed: When the 1Password extension is enabled (even with passkeys disabled), Bitwarden apparently does not get the chance to register its passkey handler anymore, and every request falls through to the browser/OS default implementation (macOS in my case).

There's a theory being discussed in https://github.com/bitwarden/clients/issues/20973, according to which 1Password has recently started preventing overrides of the navigator.credentials.get/create APIs. I can't speak to the accuracy of that, but if this is true, I'd consider it a pretty aggressive approach:

At the very least, disabling the "offer to sign in with passkeys" option in 1Password should disable this new "blocking shim" behavior, as there is absolutely no reason for it in that scenario.

Beyond that, I'm also not sure that preventing other API shims from being installed is justified in the first place: Couldn't 1Password instead offer similar UX to Bitwarden, i.e. always show a blocking pop-up with an option to select a passkey (if any) or to defer to the next implementation in the chain, whether that's the browser/OS implementation or another password manager shim? This doesn't leak any passkey presence information either and seems less aggressive than just locking out the competition.