Passkey authentication doesn't abort on signal

I am encountering this issue as well. I am designing a login form that allows the user to either login with email, or passkeys. The 1password passkey dialog shows correctly. The user can choose to use email instead, in which case we abort on the abortController. At this point I expect the 1password passkeys dialog to close. However, it does not. After the user logs in with email we take them to the app. When they logout, the stale, non-cancelled passkeys login attempt lingers. The browser thinks at this stage that the passkeys login with 1password failed, and moves onto the next browser based passkey login flow.

I propose that when the extension receives the abort signil it should close and properly abort the attempt.