DOM uses server-side ActiveX during playback, and allows you to locate content on a Web page that uses the HTML layout more explicitly. The DOM strategy is an alternative capture strategy that makes use of the Document Object Model used by many browsers when displaying HTML page content. This Document Object Model and its published API is used by UA in conjunction with server-side ActiveX technology to query, modify, and extract desired page content. When you select the DOM format, you see a sequence of captures from the page. The captures start from the HTML feature closest to the selected item, and roll outwards. For example, clicking on some text embedded in a row of a table, embedded in a page, results in the text being displayed, then the row, then the table, and then the page. The actual “unwinding” depends on the actual HTML structure of the page.
This capture strategy is most effective when the content of the site is static and stickiness of the content is not an issue. Often, it is the most effective approach when defining the second and subsequent captures in a Continuous Capture portlet.
If required, the DOM strategy can also be combined with client-side ActiveX navigation (NavACX) to capture pages that also use JavaScript heavily and as a result are not able to be captured using the normal navigation (non-NavACX) approach (or for pages that do not capture for other reasons).
It is not necessary to couple it with client-side ActiveX NavACX–that is required only when JavaScript or other rendering approaches in the browser prevent normal navigation and capture. Selecting NavACX alone does not automatically result in server-side ActiveX being used at playback. Server-side ActiveX is only used when the DOM format or ACX are selected.
To use this functionality, when creating a new application, in the Mobile Web Studio – New Web Element window, select DOM from the Format drop-down list.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
