This bug report details an issue in Firefox where selecting the incorrect 2FA hardware key results in an unhelpful “blank” error dialog, unlike Chromium which provides a clear, descriptive message. supermathie provided screenshots comparing the two browsers, noting that the application fails to properly handle the specific error Firefox returns.
Later in the thread, sam asked if the issue persisted. supermathie confirmed it remained problematic, although the error was no longer completely blank. They shared a screenshot showing a technical InvalidStateError (“An attempt was made to use an object that is not, or is no longer, usable”), which is not user-friendly.
In a subsequent update (post 16), supermathie demonstrated that the Firefox error handling remains opaque, displaying generic or confusing messages across multiple steps, while Chrome continues to provide a clear reason for the failure. The core issue is the lack of proper error mapping and user-friendly messaging for Firefox-specific 2FA failures.
When 2FA is enabled but you use the wrong security key in Firefox, you get this “blank” error:
It’s not apparent what’s happening. Chromium handles it better:
We apparently aren’t handling well the error that Firefox gives back to us.
Is this still an issue @supermathie ?
Yeah… this is not a good (understandable by the user) error but at least it isn’t blank:
InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable
