I’ve seen password managers fail to detect password fields because the frontend devs thought whatever stupid piece of React crap they vomited from their keyboards was better than using standard html fields for their intended purpose. It’s not very common, but it happens. Credit card fields are also a big mess for the same reason. Half the time bitwarden’s best guess at auto filling those results in some absolute soup that makes no sense.
I’d also like to take this opportunity to send my warmest, most sincerest fuck yous to all the UX designers who think it’s a good idea to fuck with navigation. Don’t prevent me from opening shit in a new tab. Don’t just scroll the page up to the previous h1 when I try to go back. Who the hell do you think you are?
I’m a developer that doesn’t fuck with the fields! ✨ I can’t stand JavaScript-based validation either, I use HTML attributes for basic pre-submit validation then do the actual validation on the backend.
I can’t stand the fucked up forms either.
Auto type doesn’t rely on password fields classification. Auto fill does
In KeypassXC you click on the field where you want the password to be entered, then click into the password manager and do auto type.
KeypassXC will then minimise and type the password for you.
I do this a lot when replacing 20+ character passwords in remote desktop sessions.