This topic lists things you should consider when using Netscape 4.7x to test HTML applications and Java applets in Functional Tester, particularly in cross-browser situations.
To test applets, you must use the EMBED tag and not the APPLET tag. EMBED tags do work with the Java Plug-in.
Before the first record action or playback on the page, use StartApp to load the HTML page that contains the Java applets . If you do not, the first record action on the browser loads Functional Test code into the browser.
An HTML application that relies on the use of the .id attribute of an HTML test object may not be cross-browser compatible. The .id attribute is not available as it is on other browsers. Functional Test uses the .id property to include the test object in the test object map. If the test object map does not contain the test object, the associated script cannot be used across browsers.
Functional Tester does not recognize Java applet objects within forms as children of the form. They are recognized as children of the document. This difference in the object map hierarchy affects cross-browser compatibility.
INPUT elements, such as text boxes and list boxes, are not visible except when contained within a FORM element. In this case, Netscape 4.7x, itself is not cross-browser compatible. The .name property is available only on FORM elements and A (Anchor) elements. In all other cases, the .name property has a blank string value.
Functional Tester does not include text node elements in a test object map. A text node becomes a mappable object only if its parent object is not mappable and the .hasScript property of the parent is true. A true value indictes that a Java script is associated with the text node, but there is no way to get the .hasScript property. Note: Internet Explorer and Netscape 6 and 7 are not strongly cross-browser compatible in this area either.
The .hasScript property is valid only for INPUT and A (Anchor) elements. For all other elements that support .hasScript, the value of this property is false.
The .disabled property for ToolbarButtons is always false. There is no way to determine the state of these buttons.
Terms of use | Feedback
(C) Copyright IBM Corporation 2002, 2004. All Rights Reserved.