News for hackers. Stuff that matters.
Re:Don’t Get Clever with Login Forms by tylerl on Friday February 15, 2019 @02:23PM (#19173881)
Actually this is necessary in order to support federated auth.

Password managers have already figured out how to support this transparently, so it's a non-issue anymore... Including even Chrome's built in manager, which is not exactly cutting edge. If yours can't cope then it's a sign that your software isn't being actively maintained very well.

Re:Don’t Get Clever with Login Forms by icebraining on Friday February 15, 2019 @02:33PM (#19173977)
Yeah, haven't had problems with Firefox's manager either.
Re:Don’t Get Clever with Login Forms by krferriter on Saturday February 16, 2019 @02:16AM (#19177517)
Why is it a requirement to have two separate views? Why not just do the check when the user leaves the username textbox. I don't see the reason for the other page to be displayed separately.
Re:Don’t Get Clever with Login Forms by __jal on Friday February 15, 2019 @03:23PM (#19174371)
1Password has gotten confused a few times for me. (No way I'd ever use Chrome's. Or Apple's, for that matter.) Although now that I think about it, I think not in a while.

Still annoys me - a classic example of offloading the costs of technical decisions on the user, even if those costs are "just" mental energy and a page load. At the very least, if you feel you need to do this, make the login pages very, very lightweight. One I log in to daily has huge background images that are utterly, stupidly useless, wasteful, annoying and for some reason uncacheable.