Native Replay

This topic applies to Internet Explorer only. For the other browsers, Silk Performer does not provide native replay capabilities.

The concept of native replay makes replaying a script more reliable. This is achieved by using Windows API-level events instead of JavaScript events for frequently used functions.

In the context of native replay we are using two special terms: native replay and legacy input mode. Note that native replay is the opposite of legacy input mode. If you turn on legacy input mode, native replay is automatically turned off, or the other way around. In this sense, we can also distinguish between native functions and legacy functions.

Native functions are using Windows API-level events.
Legacy functions are using JavaScript events.

The following functions can be called legacy functions, since they all have a native equivalent. If one of these legacy functions is detected during replay, then ...

BrowserClick is replayed like BrowserNativeClick
BrowserDoubleClick is replayed like BrowserNativeDoubleClick
BrowserSetText is replayed like BrowserTypeKeys
BrowserSetPassword is replayed like BrowserTypeKeys
BrowserMouseMove is replayed like BrowserNativeMouseMove

If a native function cannot be performed instead of the legacy function, the legacy function is used as fallback and a warning message is logged. This can be the case if, for example, no mouse position can be determined to click the element.

Native replay is enabled by default. You can disable it in the Profile Settings: Click Settings > Active Profile > Web (Browser Driven). On the General tab, enable Legacy input mode. Alternatively, you can add the following function to your script: BrowserSetOption(BROWSER_OPT_LEGACY_INPUT_MODE, true)

Legacy input mode is enabled by default for all project profiles created with Silk Performer 9.0 or earlier.