the basics as it relates to the Change Property dialog, you can begin to see the benefits it exposes. Beyond the simplicities of working with text fields, the Change Property dialog also supports the following functionality: Type of object: Select from a list of eleven supported objects. The objects that can have properties set include layer, div, span, image, form, check box, radio button, text field, text area, password, and list/menu. Named object: After you select the type of object you want to change the property for, the objects, if they exist within a form on the page, will appear in this list. Property: Select: Customizable properties for the selected object appear in this list. You might also want to choose your target browser from the menu to the right. Property: Enter: Although Dreamweaver includes common customizable properties, other less-used properties must be added by hand in this text box. New value: Enter the new value for the customized property in this text box. Check Browser It's considered common practice in web development to create pages suited for the variety of browsers currently available. The reason for this is simple: Users who visit your website using Internet Explorer 6.0 will have a much richer experience than those visiting your website using Netscape 4. To accommodate both users, you might decide to create two different websitesone that includes limited functionality and is mostly text-based, and another, a much richer design, that could potentially include CSS, JavaScript, and perhaps Flash animations. The dilemma is that you'll need some mechanism for detecting the type of browser the user is using to visit your site and then react to that discovery by displaying the appropriate content. The Check Browser behavior does just this. To demonstrate this behavior, follow these instructions: 1. With your cursor in the same page we've been working with, insert a new Button form object by clicking the Button icon from the Forms category of the Insert bar. 2. When the Add Form Tag dialog appears, click No. 3. With the Button form object selected, change the Action to None so that the button doesn't try to submit or reset the form when it's clicked. You can also change the Label to read anything you'd like. I'll change mine to say Check Browser. 4. With the Button object selected, choose the Check Browser behavior from the Add (+) menu in the Behaviors panel. The Check Browser dialog appears. 5. The dialog allows you to check for Netscape versions before or after 4.0 and for Internet Explorer versions before or after 4.0; you can react accordingly by specifying the URL of the web page you want to use if the browser is 4.0 or later and an alternate URL if the browser is before version 4.0. A third drop-down menu specifies which URL to redirect to if it's any browser other than Netscape or Internet Explorer 4.0. To test the functionality, let's add the path index.htm to the URL text box and altindex.htm to the Alt URL text box. When you finish, the results will look similar to Figure 10.11. Figure 10.11. Customize the Check Browser dialog so that it goes to index.htm if the browser version is Netscape or Internet Explorer version 4.0 or greater. 6. Click OK. 7. If the selected event isn't onClick, change it to onClick now. Based on our additions, when we click the Check Browser button in Internet Explorer or Netscape versions 4.0 or later, the page is redirected to index.htm. However, if we click the Check Browser button in Netscape or Internet Explorer