@Nail1684 I’ve logged a ticket and opened a PR to address the issue with the labels on the navigation buttons not being translated.
Shouldn’t need to be translated via Crowdin as we are using previous keys, which are likely already translated in most supported languages.
Kind regards,
Daniel
FYI, I am not able to reproduce this issue (Bitwarden extension 2024.11.999, Chrome 131.0.6778.71, Windows 11 23H2 22631.4460), either in Light mode or Dark mode, in an English-language UI. Maybe try disabling/enabling or uninstalling/reinstalling the extension?
@Kevin_Harris I would like to offer a suggestion for how to improve navigation in the new UI. It seems that the UI structure has four top-level pages (i.e., the “Vault”, “Generator”, “Send”, and “Settings” tabs), in which it is possible to switch tabs using the navigation bar at the bottom, and also to switch accounts or lock/log out (using the profile avatar displayed in the upper right corner). However, if one opens any lower-level page, then access to the bottom navigation bar and the profile avatar is lost.
As a result, I’ve often found myself frustrated by the inability to quickly access these UI elements, and to quickly return to the Vault view. This is especially problematic when one has drilled down into a low-level page such as Settings > Notifications > Excluded Domains or Search > View > Edit > Attachments, so that several repeated clicks of the “Back” (<) button are required to return to the main Vault page. The problem is exacerbated by the new “persistent UI” functionality, because closing and re-opening the extension no longer returns to the Vault page as a default.
My suggestion would be to add a “Home” button to all lower-level pages (i.e., every page except the top-level “Vault”, “Generator”, “Send”, and “Settings” pages), which would return the user the Vault page. On the lower-level pages, there is currently only a single icon (the pop-out button) in the upper right corner, so this would be a good place to add a “Home” button, as shown in the mock-up below:
@Nail1684 Thanks for reporting this. I was able to reproduce and this should be addressed with [PM-15148] Fix toggle entry not displaying correctly on non-English clients by djsmith85 · Pull Request #12088 · bitwarden/clients · GitHub
Feature Request: Home Button
Hi everyone " i’m new here and i come from 1P" one thing i like about 1Password its that you can Customize, “Your’e STUFF”
So I would like to suggest re-TAP-And rename it a home, where you can customize things like important things or add other items etc.. It would be great if we could customize some things!
What do you think guys?
Please allow an option to include more than one number when generating a username from a random word. It would be nice to include anywhere from 1–6 numbers in the username. For example, I created the username for this forum using the old Bitwarden extension, which allowed four numbers at the end.
If a Relying Party (on a non-excluded domain) request passkey authentication while the extension is locked, then the extension is expected to prompt the user to unlock the vault, with an option to “Use your device or hardware key” for handling the passkey authentication instead of using Bitwarden. If the user unlocks their vault when prompted, they should be presented with the matching passkeys available in the Bitwarden vault, and be allowed to select one for the authentication ceremony. This is the way that in works in the production version of the browser extension, but this workflow is completely broken in the beta extension (version 2024.11.999).
When the Relying Party requests passkey authentication while the beta browser extension is locked, the following pop-out window appears:
Note that the bottom of the UI is cut off in the pop-out window (pushed below the fold by the vast expanses of empty space in the UI), but even if one uses the scroll bar (or resizes the pop-out window) to reveal the full contents of the UI, there is no option to Use your device or hardware key.
If the user proceeds to unlock the vault, then the pop-out just opens to a static “Vault” page. There is no option to use any stored passkeys, and the floating pop-out window does not automatically close after unlocking has been completed.
The beta version is now in production (version 2024.12.0), so I am closing this thread. Additional comments should be posted in the community forum feedback thread linked below:
Alternatively, you can create specific feature requests or post formal bug reports in the appropriate locations
