I ran into this just the other day, a site wouldn’t let me paste my password into the “confirm password” field when signing up. Had to resort to editing the HTML properties because there’s no way I’m manually typing in my long-ass randomly generated password.
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?
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.
You just gave me a hideous flashback to the bitlocker carnage a while ago, and having to type in what felt like an endless stream of characters that some poor sod in IT was reading me over the phone, probably for the 100th time that day.
I ran into this just the other day, a site wouldn’t let me paste my password into the “confirm password” field when signing up. Had to resort to editing the HTML properties because there’s no way I’m manually typing in my long-ass randomly generated password.
Does your password manager not support auto type?
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?
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.
You just gave me a hideous flashback to the bitlocker carnage a while ago, and having to type in what felt like an endless stream of characters that some poor sod in IT was reading me over the phone, probably for the 100th time that day.
It does, but (as far as I know) not for putting a newly generated password into a signup field.
Even with CTRL+V? 99% of the time when I encounter this they only block right click, but CTRL+V will work for…reasons
Yep, even Ctrl+V didn’t work. I guess I shouldn’t be surprised considering it’s a government site (the signup for federal student aid).