Can you do exercises on parallel project 1 and 2 please. CLIENT SIDE VALIDATION

6.15 Exercises on the Paraliel Project 221 taiExercises on the Parallel Project main goal of th A an alidate, using regular expressions, the data input by a user before sending al of this chapter was to show how JavaScript can be used on the elient Tne side to data to a server In of Dt he tion of the last chapter you developed two forms, one for choosing prod- ices that your company offers, and one for getting feedback on customer that data to sstisfaction cts or i.Now you need to make those forms as secure as you can by checking as the input as you can to make sure it is nothing other than what you expect of arace e So, complete the followving exercises e a JavaScript script that validates all user entries for which it makes sense do so in the form that permits your customers to choose a product or service. Be sure to inform the user if any data entry is invalid. Once all input has been validated, display to your customer some relevant output related to the data that has been entered. A typical display would be a summary of the items ordered, the numbers of each item, the cost of each item and the total cost. 2. Write a JavaScript script that validates all user entries for which it makes sense to do so in the form that permits your customers to give you feedback on their experience with your business. Report to the user if a particular entry is invalid, and be sure to tell the user that everything is OK if that is the case. Some of your data validation and computation can be modeled on what you see in the text examples, but of course some will be peculiar to your particular business as well. 6.16 What Else You May Want or Need to Know 1. The official name of JavaScript is ECMASeript, although almost no one actually uses that name. See the References for further information. 2. When you view JavaScript code that is embedded in an XHTML document, especially code that you find out there on the Internet, you may see that code enclosed in a comment block. We could have done this with our embedded code shown in Figure 6.1, and if we had it would have looked like this