unique name to be given to the Image Field form object in this text box. As with Button form objects, naming Image Field objects isn't the biggest of priorities, so we'll leave ours with the default value of imageField. Src: Displays the source path of the Image Field form object. Alt: For accessibility reasons, you'll want to enter the alternate text to be associated with the Image Field form object here. We'll add the text Click Submit. More information on accessibility can be found in Appendix A, "Accessibility." Align: Select an option from this menu to set the alignment of elements around the Image Field object in relation to the Image Field. For instance, selecting Left from this menu aligns the Image Field to the Left and all elements, including text, around the Image Field's right. Edit Image: Click this button to launch the external editor specified for the Image Field's extension type. Remember that these external editors are specified in the File Types/Editors category in the Preferences window. Class: When working with CSS, select a class from this menu to set the overall style of the Image Field form object. We'll leave ours blank. File Field One of the most under-used form objects available in Dreamweaver is the File Field form object. You can use this form object as a way of enabling end users to browse their hard drives for a file in order to upload that file to the server for processing. The File Field object, which is really just a Text Field with a Browse Button, is shown in Figure 9.17. Figure 9.17. Use the File Field form object to allow users to browse for and select files on the hard drive for uploading to the server. [View full size image] NOTE Initially the File Field seems like an object that would be widely adopted by web developers. The downside to the File Field is that it takes a lot of know how and code to get it to work server-side. The difficulty in integrating the File Field with server-side applications is the primary reason this form object is rarely used. Hidden Field The Marketing department's friend, the Hidden Field form object is a common way to persist client-side data from page to page without the end user seeing or even realizing it. I say that this form object is the Marketing department's friend because this form object was used to death in the late 1990s' dot-com web-marketing crusade to sell unneeded and worthless software to unsuspecting web newbies. The scam was simple and involved nothing more than forms, form objects, and a couple of Hidden Fields. Typically starting with an email (spam) advertising the next best "free" software, unsuspecting users would click the accompanying link to visit the site offering the "free" software. Initially, the offer seemed legitimate, asking the user only for their email address with a button promising that the next step was the download. The unsuspecting user would click the button to download and be taken to a second page requiring more information such as name, address, age, and so on. The user, believing that the company already had their email address and that they will get spammed to the nth degree if they don't complete the process, cautiously enters more information and clicks yet another button that promises the next step is in fact the download. But to no avail; the user is now required to enter a credit card number and expiration date to purchase the $4.99 software which they initially thought was free. Fearing retaliation from the dastardly company, the user is