Forum Discussion

emailvision_Sup's avatar
emailvision_Sup
Occasional Contributor
14 years ago

different behavior between aliase and the same direct path

Hello, I have a strange behavior that I can't clarify. I'm testing a flex application embedded into a web page. In my script, in some specific cases when I call directly the item (ie: Sys.P...
emailvision_Sup's avatar
emailvision_Sup
Occasional Contributor
14 years ago
Hello Allen,



thanks for your answer. Using the breakpoint I see the same object. I'm mostly using the direct call for object because some of them are not working by mapping in the flex embedded.



for example I've tried mapping to click on a listItem of a dynamic dropdown list in the flex and I can use the Sys ref without problem but the mapped object is not clickable even with the same sys reference. 



direct ref: 

Sys.Process("iexplore", 2).Page("https://XXXX").Frame("bottom").Object("myFlashContent").List(1).ListItem("New_Email")

Alias:

Aliases.iexplore.pageCampaignCommander.frameBottom.objectMyflashcontent.List(1).Click();



And via alias or namemapping I can't even see the list, when clicking on it  I get message '...underkying object missing...' because the drop down list is a non permanent item.



It looks like namemapping and aliasing is not stable for dynamic content inside flex. Please note that I'm currently testing my application just with "accessible true" in options but without the flexclient.swc or automation.swc (I'm waiting for some internal support to clear that point). I don't know if this can explain the behavior I'm currently facing.



Thanks,

Nicolas.