Additional files need to be specified when embedded objects will be downloaded by JavaScript or other techniques that are not covered by the Silk Performer HTML parser.
The URL to download can be specified relative to the base URL of the document that is downloaded by the subsequent page-level API call.
Example:
WebPageAddUrl("http://www4.company.com/images/mastercard.gif"); WebPageAddUrl("http://www4.company.com/images/visa.gif"); WebPageLink("Choose payment"); The same script in SilkPerformer, assuming the WebPageLink call downloads the URL http://www4.company.com/user/6543/payment.asp: WebPageAddUrl("/images/mastercard.gif"); WebPageAddUrl("/images/visa.gif"); WebPageLink("Choose payment");
While WebPageAddUrl is a context-less function, the use of relative URL's minimizes the risk that a URL parameter will contain state information.