Forum Discussion
HKosova
Alumni
14 years agoHi Pasha,
It looks like the root cause of the problem is that your Internet Explorer version (8 or 9 - which one, by the way?) spawns multiple processes with different indexes, so you end up with iexplore, iexplore1, iexplore6, etc., and the web page belongs to different process instances at different times. That's why, the web page can't be identified properly.
To avoid the problem, you need to configure Internet Explorer to use a single process as described here:
Disabling Loosely Coupled Internet Explorer
Once you have that fixed, you should be able to get the current page URL using the following expression:
(The URL expression I suggested in my previous post is incorrect.)
To verify the URL using a checkpoint, you can use code similar to this:
Let me know how this works out for you.
It looks like the root cause of the problem is that your Internet Explorer version (8 or 9 - which one, by the way?) spawns multiple processes with different indexes, so you end up with iexplore, iexplore1, iexplore6, etc., and the web page belongs to different process instances at different times. That's why, the web page can't be identified properly.
To avoid the problem, you need to configure Internet Explorer to use a single process as described here:
Disabling Loosely Coupled Internet Explorer
Once you have that fixed, you should be able to get the current page URL using the following expression:
// using Name Mapping:
Aliases.iexplore.FindChild(["ObjectType", "Visible"], ["Page", true]).URL
// not using Name Mapping:
Sys.Process("iexplore").FindChild(["ObjectType", "Visible"], ["Page", true]).URL
(The URL expression I suggested in my previous post is incorrect.)
To verify the URL using a checkpoint, you can use code similar to this:
var currentPage = Sys.Process("iexplore").FindChild(["ObjectType", "Visible"], ["Page", true]);
aqObject.CheckProperty(currentPage, "URL", cmpEqual, "http://itglobal.ru/products/ow/manual/manual.aspx");
Let me know how this works out for you.