#2139 Autotype sent wrong entry to webpage even after removing all target windows

[James]

Today I pressed Ctrl+Alt+A to initiate autotype in a Firefox tab for a website.
KeePass entered the wrong KP entry.
I have seen this before in the past very occasionally and I have always assumed it is because I had somehow registered a webpage to autotype against the same entry as another.
Today's though was very strange.

I created a new autotype for the webpage in the KP entry for that webpage.
Sure enough when I autotyped, KP gave me the option for the correct entry or the old one being entered.

That's when I knew something was unusually wrong - the entry which was entered into the webpage was one I have not used for several years - from before the website it got auto-typed into existed.

I edited the KP entry for the old website - deleting the autotype target windows.
Still when I went to autotype it gave the wrong entry as an option (but at least now the option box was a point at which I could cancel before the wrong text was plastered across the other site.

I saved the database. Still it was presented as an autotype.
Only when I Disable autotype for the wrong entry did it stop trying to present it.

I think there was something off in my Firefox instance.
Possibly confounded with a VPN which I had to disable to use the site properly.
I restarted Firefox and KP is no longer presenting the wrong entry.

It is quite odd and a little disturbing so I thought I'd pass you the info.

James

[James]

Sorry - this should be for KeePass 2 - since restarting Firefox SourceForge kept the text I had started writing but must have reset the dropdowns.

[Paul]

KeePass also matches the entry title. Maybe the title is "Firefox" so it will match every website?

cheers, Paul

[James]

Thanks Paul.
I have only ever populated the auto-type Target window field by using the dropdown which is auto-filled by KeePass for the various open windows - assuming a simplistic manual entry could lead to a misattributed one.

(Annoyingly these days Zoom's ZPToolbarParentWnd is always at the top when it used to be the last one being used).

I see I can type into that box but I assumed the text needs to be specific and that what I see might be a friendly text name for the actual technical ID being used to somehow identify the specific window, current page it relates to.

In this case, it did not simply say Firefox - it was quite specific but did have the word Firefox in there.
If that had been the issue I should have thought that for the many years it has been sitting unused in KP it would have at some point auto-typed before on one of the many times I enter things into Firefox, if not this particular website (which as I mentioned is quite new) and I would have noticed as the username is quite unusual.

Another thing to throw in in case it could mess with Firefox is I'm using Mozilla Multi-Account Containers, though again I don't see why that would cause this.

Can you tell me a little more about the Target window field please?
I had wondered how it identifies which exact window and page (sometimes it seems to pick up the specific page (e.g. this ticket) I'm on when I click to login, when I just want to tell it anywhere within that site (SourceForge) or I have to create a new entry for the site when not on that page.
I had wondered how KP identifies which site it wants and which many other Firefox pages to ignore - hence assuming it's doing more than going just by the text I can see in the dropdown.

I have just had a look again and even though the auto-type for the wrong entry has no Target windows added, with auto-type enabled KP presents that entry alongside the correct one.
The URL is definitely not like the one that should be presented.
I see nothing else to make it think they are associated.

I used to wonder if KP can execute an auto-type from the URL field but now's the time to learn more about the auto-type feature.

James

P.s. please change the attribute of this ticket to reflect KP2 not 1.

[Paul]

Go to Tools > Options > Advanced, Auto-Type.
Turn off all settings and test.
Turn on the 2 default settings (see pic) and test.

cheers, Paul