New answers tagged

0

EDIT: oops, I misunderstood the question. You don't want to 'disable' Caps Lock because how exactly would you communicate to users that this mode is unachievable? Some users may not know how to use Shift to temporarily enforce uppercase, and may not be able to type their password anymore. Besides, it seems unintuitive that a functionality of your keyboard ...


3

The core reason that you don't want to do this is because, as a general rule, any time you override the standard behavior of a users device, you open yourself up to a bad user experience . . . particularly if you do it without any kind of notification. Overall, within your application, standard control behaviors should continue to behave the way that the ...


0

It's a good practice because any good UI should tell you of its current state; It's not so much of a warning, more of a notification. Accepting multiple variants of the password is really bad; you're essentially reducing the complexity of the password. By disabling caps lock you're taking control away from the user and the only reason seems to be just to ...



Top 50 recent answers are included