Ask a Question

Element slides away on highlighting

amit_bansal
Occasional Contributor

Element slides away on highlighting

While using object spy, I am selecting the element by glyph. The target address is filled in the in the object textbox. But when I click on highlight, the element on the modal window slides down and is not "visible on screen".

24 REPLIES 24
amit_bansal
Occasional Contributor

I was trying to use the mapped name as suggested by you (Considering Find Child was refreshing and scrolling the modal window). But mapped name refer to two different elements. I tried deleting the mapped names and saving different mapped names for the two elements. They again acquired same mapped name.

amit_bansal
Occasional Contributor

I have tried saving object to a variable and then running code snipped using that variable but it always scroll down the element and result remains the same and log message is again "There was an attempt to perform an action at point (47, 15) which is transparent or out of the window bounds.". In my opinion, other case could be the element is coming behind the footer that is a panel and cursor is clicking on the footer panel.

What you need to do then is work with your NameMapping and make sure that the objects are identified uniquely.  Basically, what's happening is that your mapping is not specific enough... that there are two components on screen that match your mapping.  You will need to correct this.  This will take time.  Look at ALL properties of the components.

ALSO... NameMapping works from the hierarchy as well... so, if there are two different components, they must have different parent objects.  It's possible that you have Extended Find turned on for your component which is why it's finding both items as the same mapped item.

The same is the case for your FindChild... you are not being unique enough in the criteria you are using for finding the child object.  You may need to start with a different parent, or add additional property/value pairs... or both.

 

BUT... the root cause of the problem, as you determined, is that your methods for finding the component are not specific enough to uniquely identify it.  Fix that... and your problem goes away.


Robert Martin
[Hall of Fame]
Please consider giving a Kudo if I write good stuff
----

Why automate?  I do automated testing because there's only so much a human being can do and remain healthy.  Sleep is a requirement.  So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.

Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available
amit_bansal
Occasional Contributor

I had mapped them uniquely but now the issue I am facing is that the element is coming behind the transparent footer panel and when curser clicks on it, it clicks on panel rather than clicking on the element.

Then you need to scroll the element so that it scrolls to the top of the page... Make sure that scrollIntoView has the "true" parameter... and I would actually put that on the modal itself, not just the drop down control.


Robert Martin
[Hall of Fame]
Please consider giving a Kudo if I write good stuff
----

Why automate?  I do automated testing because there's only so much a human being can do and remain healthy.  Sleep is a requirement.  So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.

Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available
cancel
Showing results for 
Search instead for 
Did you mean: