@Joe_G I don’t disagree that PR #5384 has introduced some bugs, while other behaviors that have manifested as a result of this change fall more in the category of “unintended consequences”.
I don’t understand your issue with tuning of URI Match Detection Rules; this feature exists for a reason.
As it is, you are currently giving Bitwarden the following instructions:
- Automatically autofill every time a page is loaded.
- Autofill on every page in the domain, not just the login page.
- Re-prompt the master password before autofilling.
If you insist on all three requirements, then the natural consequence is that you will be presented with a master password prompt every time that you navigate to a new page in the matching domain. In my opinion, it is a bug that the prompt comes in the form of a new browser windows even when the browser extension is already unlocked, but if that bug is fixed, then you should still get a prompt within the browser extension pop-up each time that you load a page. The solution is to relax one of your three mutually incompatible requirements.
If you don’t want to reconfigure your URI Match Detection settings, then an alternative would be to selectively disable the auto-fill on page load option for those domains that have the master password re-prompt option enabled. You might even be able to write a script that automates this process.