Web237_Learning_Team_Project_Paper

tags to provide the copyright content. The prototype website, when viewed using different web browsers does show a few slight differences depending on the version of browser. Comparison tests were done using Google’s Chrome browser, Mozilla’s Firefox browser and Microsoft’s Internet Explorer Browser. There are some minor differences between each browser but nothing very significant. All browsers rendered the page very similarly in terms of formatting, color, text font, text size, text alignment and image alignment. There are some very minute differences such as font density being slightly higher in the Chrome browser and descending to Firefox then Internet Explorer. This is presumably due to the differences in how the browser displays fonts. Unless compared side by side, it is barely perceivable. The image borders are slightly rounded for Chrome and Firefox while Chrome seems to have almost cut off corners. Internet Explorer has no rounded image borders and displays with hard right angles. This could be due to how the browsers interpret and apply CSS elements. Color and thickness are identical so it seems isolated to just the corners. Most of Internet Explorer’s page rendering does seem slightly sharper in all areas save one, the contact form. The edges are softened compared to Firefox and Chrome which display near identically in that area. The resolution differences must have something to do with the rendering engine itself since there is no perceivable change in the code. One final, yet very important difference was mentioned previously in another section.  . As the viewer of the site you’d never know it unless it was missing. This piece could easily be missed by the developers and could cause problems. The fact that Internet Explorer does not include this as a standard functionality for the browser creates an undesirable situation for developers where more work needs to be done on their side to get the page to render properly, while Firefox and Chrome require no such extra work. Over time, the constant enabling of Explorer could become a frustration and present other issues down the road. Here is what the code looks like: JavaScript The JavaScript shopping cart uses function calls to run logic loops for decision making. The shopping cart in this site is designed to use the browser cookies to create an array used to store the information of selected products. The AddToCart function uses selection control structure (if, else) statements to check if the products fields are null or empty and if it is empty to clear the array associated with that field by using statements like ." When a field has information in it such as items number, product descriptions, the if statement then moves to the else statement and the string is set to validate the quantity of inputs box. There is a sub-function designed to validate the quantity inputs from user, and also display the total amount whenever user clicks “update cart” button. In addition, the decision-making statements; using both for next loops and Boolean logic, allow the functions to calculate total cost, taxes, and shipping as well as making changes to items in the cart like changing quantity and deleting items. An example of adding or removing items to cart that used in this site as follows: Another function used in this site is a decision-making loops that let the form validation and alert messages letting the user know if he or she missed required information or inputted invalid information. A good example of this is the radio button verification used to make sure the user selects the proper tax selection. If the user does not select an option, they receive an error message and it’s prompted to make a selection. Though this method of creating a shopping cart is easier to set up and works on the client side, it is important to remember that with big inventories that a CGI controlled shopping cart with the ability to save the cart information on the server for later retrieval is a much more secure way to do business. Web Standards * The professional web development standards used in the development of the team’s prototype would mostly be HTML 5, CSS 2, and 3. Article and section tags were used in the in the HMTL document as well as rounded corners in the stylesheet. It was 2007 when the W3C joined up with WHATWG to develop HTML 5 (W3.org, 2011). There have been multiple revisions of HTML 5 since then. * The full code of the index page is HTML 5 starting with . The main sectioning of the page follows HTML 5 guidelines. * **Awsome iPhone Sales* ******