![]() ![]() if (hasInputBorder()), "That's what I call a password!"), There are a lot of “ifs” here, and the code is not very easy to read. ![]() The following code demonstrates how this could be done by DOM manipulation. We might also show a smiley face when a password is sufficiently strong. If the password is weak, the input box should have a red border and should display a warning message. If the password is OK, the input box should have a green border and should display a nice message. Let’s take a look at a simple example of evaluating the strength of a password. jQuery also brought significant advances to front-end web development, as it provided simple and effective out-of-the-box capabilities such as client side validation, modal windows, alert messages, animations, and even Ajax-based partial page updates. Developers started writing significant amounts of code that was executed in the browser before a request was sent to the server. We needed a quick, snappy, and responsive interaction with immediate impact on the UI. Reloading the whole page, when just one part of it changes, was ineffective and slow. However, web applications grew in their complexity and user demands of the UI/UX were advancing as well. ![]() Applications did not have to worry about the user state and each view could be regenerated by sending a new request to the server. Subsequent user actions (such as clicks, form submissions, etc.) would trigger the same flow again. The browser would send a request to the server, all application logic would be executed on the server, and a full HTML view would be sent back to the browser for presentation to the user. Not that long ago, web applications had a much simpler data flow. ![]()
0 Comments
Leave a Reply. |