New answers tagged password
I'm gonna answer this with some information that @Peter provided in the comments: Like he said, there is a lot of information widely available about why you should not use Password Masking and how it has a negative spin on UX. Here are some resources from people who really know their stuff in terms of UX. Jakob Nielsen has an article on why you should ...
Not sure if it is any good, but for it's worth, this is what I came up with. https://jsfiddle.net/qqqkzkx1/embedded/result/ If you have any scripting recommendations or constructive criticism, please post it http://codereview.stackexchange.com/questions/87980/inline-editing-for-modifying-field-that-requires-supplementary-inputs-such-as-p. Thank you
Prior to my mock-up of how I think this could work, I'd like to say I'm not really a fan of in-line overlaid prompts such as this. They are stylish but they have a restrictive user base (i.e. generally web/mobile confident users). Older/less confident technology users may be confused by changing elements. Furthermore, I think you should consider people who ...
Neither approach If possible, settings should be on one page, and you should not have to re-enter your password. There are several ways to do this. Here are two: In the second approach, the password form is hidden and is displayed when the user wants to change the password.
This depends on the level of security you require. Perhaps you can conditionally require the password depending on which fields the user has altered?
Top 50 recent answers are included