I'm wondering if there is any workaround to issue a second-browser activity without interfering with the current browser activity.
Describing in real browser terms, basically I want to perform a series of operations with my current browser window, but want to launch a second browser instance and check other urls. For example, my web app has front end and back end, when a user logged in from the front end, I can verify from the back end url that "Authentication OK". The problem is that I can't jump from front end to back end to check it, because the browser will think I've left my front end, and I can't continue on without starting all over again from log in.
It sounds complicated, but all that I want to do now is to change the following customize code
into not using ActiveBrowser, but something else (second-browser).
I hope a workaround is possible.