And today I still have no idea how it decides what credential to use when you unlock the BW browser extension.
I see it said everywhere that “it will autofill the most recently used set of credentials.” yet that is not what happens for me. I just get the same credential used each time on websites, even if it’s a login credential I hardly or even never use.
I have tested and tried all sorts of things to try and get it to just use the last credential I used, but as soon as the plugin is locked then it will unlock and use the same credential everytime, unless I delete that one. Then it picks another one at random. It almost seems like it’s avoiding the one I use most often (feels that way - haven’t tested enough to confirm lol).
I really just want to know how the browser extension it decides what credential to use when you unlock from the context menu. Because it absolutely is not the most recent (unless most recent means most recently added? Hmmm Let me test that)…nope that didn’t help.
Seemingly nothing I do short of deleting the credential that it picks each time, will change that it picks that.
This is software, so there must be code that decides how it chooses the credential to use when it’s unlocked that way. I just would love to know it… so I can stop trying to find a way to “fix” it. lol
Edit: oh and I have tried to make myself remember that if I go tot select a login and find it’s unlocked, to backup and then unlock it and then go back and select the credentials… but I use the context menu this way so much each and every day, that it’s just not that easy to stop my flow. I rarely click on the extension button on the toolbar, I just right click a field and select Auto-fill login and then the account… that’s when I discover it’s locked…
Also I do notice that the order changes for most recent in the context menu and the toolbar drop down. But it ignores that next time I unlock… I also tried favouriting the one I use the most, adding it again. Making the one I want picked more specific match (host instead of base). Moved it out of a folder, etc. Nothing so far… really hoping I am missing something here
I’ve experimented a little bit, and I believe that there may be a bug. It will take some additional testing to find a reliable procedure for reproducing the issue (which will be needed for filing a bug report).
I was just testing on other browsers and with a mate in another country on a different setup to see if I could find a setting or browser based difference.
My mate thinks it works correctly for him in FF but I just tried and was able to reproduce.
If I can help with any testing let me know. I was basically logging in with BW a few times both from the context menu and the browser icon, and then confirming the one I last used was at the top of the list in the extension and the context menu. Then I locked BW. Then from the context menu selected the Auto-fill login → Unlock your vault. And in both browsers it always selects an account I rarely use. And moves that to the top of the list (even if I don’t actually login.. just from it selecting it).
I just did more testing and I think the autofill settings may impact how this works… testing more now. It used the right one for the first time ever just now when I turned auto-fill on page load back on.
Weirdly it’s still stuck on defaulting to a single login for the site I was testing… but it’s now the one I want lol. There is inconsistent behaviour going on, or at least influenced by factors that are not clear.
If I use the autofill keyboard shortcut (Ctrl+Shift+L) after refreshing a login page using F5, the most recent account is autofilled unless I press Ctrl+Shift+L too quickly after pressing F5. If I autofill too quickly after a page refresh, the next account in line is autofilled.
If I autofill using the right-click context menu, then the order of accounts in the right-click context menu is not updated until I refresh the login page using F5 or open the browser extension pop-up.
If I autofill using the Fill button in the browser extension menu, the order of accounts in the right-click context menu is not updated, even if I refresh the login page using F5 or open the browser extension pop-up.
I believe that the third one of these will be addressed by PR #16388, and possibly the second one as well. The first issue seems unrelated.
