I'm pretty sure that bitwarden causes some page to load slow, it shows slow script warning frequently.
Now I have to disable bitwarden, and no warnings anymore.
Since the site is an internal company site, I cannot give you account to test. So I wonder can you consider adding the function to disable bitwarden on a specific site?
Bitwarden is by now the best password manager, I don't want to switch to others.
In LastPass these are called "Never URLs" just for reference - I as well need these for my work internally at my company. Besides websites that might cause performance issues, we have endpoints which are accessed without using Bitwarden (think RSA tokens) so wish to avoid "do you want to add this website?" every login to select domains and IP wildcards (https://10.12.*/, etc.)
Besides any possible performance issues, being able to disable autofill per site (or per vault entry) is a must-have. Some sites have autosaving forms, which get incorrectly autofilled by Bitwarden.
For an example of this, go to the settings of a Tumblr with asks enabled; the ask page title gets autofilled with your login email, which is then autosaved.
@Atte see #501 for this request.
We are moving away from tracking Bitwarden feature requests like this one as GitHub issues. We have created a Bitwarden Community Forum which has a section for submitting, voting for, and discussing product feature requests. Please sign up on our forums if you want to continue contributing to feature requests.
Since this was a popular feature request we have already re-created it on the forums and linked back to this GitHub issue for reference. You can vote for this feature request there if you'd like.
https://community.bitwarden.com/t/disable-autofill-on-page-load-option-for-specific-logins/22
This issue will now be closed. Thanks!
@kspearrin - thanks for this, FYI when creating an account on community.bitwarden.com, the Bitwarden browser extension 1.24.0 does not prompt to save my new login on the site. ouch. :)
@terackspace That is being fixed in next version. Currently we explicitly ignore all bitwarden.com domains on purpose. We should update that to only ignore vault.bitwarden.com
Most helpful comment
@terackspace That is being fixed in next version. Currently we explicitly ignore all bitwarden.com domains on purpose. We should update that to only ignore vault.bitwarden.com