Silk Performer's browser-driven approach relies on the webbrowser control of the primary (initial) BrowserWindow through the entire scenario of a test. To implement a particular workflow, some applications open a new child window and close the base window. If the closed window is the primary (initial) BrowserWindow of the test scenario, the internal state of Silk Performer' s browser-driven engine is undefined. This might result in unexpected application behavior during recording as well as during playback.
Add an additional BrowserWindow to your test - it will act as the new base window. The primary (initial) BrowserWindow remains unused in your scenario. To add an additional window during recording, click . Make sure to add the window right at the beginning of your recording. For existing scripts, add a BrowserCreateWindow statement right before the first BrowserGetActiveWindow statement.