But I think a blacklist where Bitwarden won’t operate, at all, on specific sites would help when dealing with issues such as the PayPal login problems.
To clarify, even if I’m not using autofill, something about BW seems to interfere with PayPal. Currently I have to disable the extension, login to PayPal, then re-enable it.
Since BW works great with most sites, being able to maintain a small blacklist of sites it ignores entirely would be nice. As in it doesn’t scan, doesn’t autofill, so as far as the site is concerned it doesn’t even exist.
Seems like a reasonable way to avoid the moving target of all the “Bitwarden doesn’t work/breaks site X/Y/Z” too.
I vote for this, it is quite annoying to have to deny bitwarden everytime I check my online banking, which I don’t want to store.
Web extension, Chrome, Win11.
However, the exclude domains definitely does not match this request. Personally I would like to have this feature because I’m developing a website and I don’t want to have bitwarden popping up and disturbing me when I’m logging in there. Therefore I would like to disable it for localhost (with strict match) but not for localhost:7080 as I have an admin panel there.
The “Auto-fill Blocked URIs” sounds like the correct feature, but it hasn’t been implemented to the firefox extension at least. (according to the linked site)
This feature request is several years old… but I would like to add to this discussion. I’ve found that the latest version of BitWarden Client (v6.X, chrome) causes significant slowdown on some web applications. I hope the BW team fixes the performance issue, but a great additional solution is to allow blocking BW from running on a site at all. The extension has the ability to opt-in to domains (site access in the extension manager). An opt-out option with be a massive enhancement.
