Use to set object and table recognition options for the DOM extension.
Primary Extension column, and then click
Extension in the
, enable a primary extension in the
Note: The primary extension must be enabled before you can click
The information that you enter on this dialog box is saved in the
domex.ini file in your
<SilkTest installation directory>\Extend directory. To avoid any confusion, we recommend that you do not have the
domex.ini file open while you are working with the
DOM Extensions dialog box.
There are several DOM extension options that are not available through the
DOM Extensions dialog box.
Show the following components area
- Borderless Table
Table check box and set a value for borderless table recognition. .76 is the threshold where
Silk Test Classic starts to recognize more objects within tables, such as images, hidden text, check boxes, textfields, and buttons.
- If checked, the DOM extension records Meta objects. Default is checked. Uncheck this check box if you do not want the DOM
extension to record Meta objects.
- If checked, the DOM extension records Hidden objects. Default is checked. Uncheck this check box if you do not want the DOM
extension to record Hidden objects.
- If checked, the DOM extension records XML objects. Default is unchecked. Check this check box if you want the DOM extension
to record XML objects.
- If checked, the DOM extension records invisible objects. Default is checked. Uncheck this check box if you do not want the
DOM extension to record invisible objects. If your browser-based application consists of pages that contain many invisible
objects that you do not need to test, then you can improve performance by un-checking this check box in order to ignore all
- If checked, the DOM extension records Form objects. Default is unchecked. Check this check box if you want the DOM extension
to record Form objects.
- If checked, the DOM extension records Text objects. Default is checked. Uncheck this check box if you do not want the DOM
extension to record Text objects. If you are testing a transaction type page with a lot of text, consider un-checking the
Text check box. This prevents
Silk Test Classic from recording many text objects, which helps your declarations to be clean. If, on the other hand, you're looking for formatting
and styles of text objects, you'll want to select this option.
- If checked, the DOM extension records BodyText objects, which is text that is not contained within an HTML tag. (In previous
releases, body text appeared as HtmlText.) Default is unchecked. We suggest keeping this option unchecked for improved performance,
particularly when recording window declarations on large pages. Should you need to record body text, check this check box.
Silk Test Classic sometimes treats body text differently from HTML text that is in an HTML tag. For example,
GetChildren() will not return body text. Also, Record Window Declarations will not highlight the window declaration of a body text object
when the cursor is moved over it, and other recorders such as Record Window Identifiers will not detect it. IsVisible() returns
FALSE for body text.
- List Item
- If checked, the DOM extension shows the text contained within
HtmlList controls in your browser. Default is checked. If mouse events are associated with your list items, check this check box so
Silk Test Classic can interact with the list items. This setting is global. However, if you want to set this option for only certain points
in your script, use
as described in
Object recognition options area
- Use Browser nearest text
- Determines how the DOM extension finds the closest static text for
HtmlPushbutton. Check this check box if you want
Silk Test Classic to use the DOM extension to find the closest static text for the objects listed above. This does not apply to invisible objects
such as XML, Meta, and Hidden; those objects do not rely on any text on a page and so it would be meaningless to try to associate
them with any objects. Uncheck this check box if you want to use the Agent to determine closest static text for the objects
- Use virtual column
Affects how the DOM extension records asymmetric tables. These are tables that use either column span or row span attributes,
or tables whose rows don't have the same number of columns. An example of an asymmetric table is a typical calendar page that
has the month of January written across the top row and the seven days of the week in seven columns across the 2nd row.
We highly recommend that you check this box if you are working with tables that have asymmetrical rows.
Check this check box if you want to create virtual columns for any row in a table. In the example above, it causes the top
row to contain one real column for "January", followed by 6 virtual columns which are blank and align with Mon, Tues, etc.
These virtual columns appear where there are none in order to complete the table and they are named virtual1, virtual2, and
so on. These virtual columns cause the table to be symmetrical.
Uncheck this check box to avoid creating virtual columns. This causes
Silk Test Classic to record the top row as the name for first column. This occurs because there is no 2nd column in the top row; Mon is promoted
to the name of the second column, and so on.
- Search whole DOM tree
- Determines how windows declarations are found. To search the entire DOM tree when you record windows declarations, check
Search whole DOM tree check box.