"Mouse over" keyword seems not working in Google chrome. #131

Activity

1. emanlove commented on Oct 9, 2012

   

   emanlove

   on Oct 9, 2012

   Member

   More actions

   @srib4ufrnd: That position seems awfully large, -12789, and in the negative too. Make sure you are using number type for arguments to the 'Mouse Down' keyword.

   For example usage should be like

   Mouse Down  ${100} ${75}
   

   noting that the arguments are using the number format ${ }. If you have something like

   Mouse Down  100  75
   

   then your arguments 100, 75 are strings and not numbers for which Robot Framework will convert those arguments to numerical position, in this example convert ("100", "75") to (68100, 7875) which is not what you wanted.
2. srib4ufrnd commented on Oct 11, 2012

   

   srib4ufrnd

   on Oct 11, 2012

   Author

   More actions

   Thank a lot @emanlove for u r explanation.

   But in our script we are not actually using Mouse Down or Mouse UP.

   The keywords we are using is "Mouse Over" & "Click Link" and we are using "mouse over" and "click link" with id based locator (not coordinate based).

   Our purpose is we have a HTML element with ID 1. When user mouse over on this HTML element user will get a drop down list with 2 different HTML elements with ID 2 and ID 3. Now user want to click on HTML element with ID 2.

   so we are trying as below
   for example: our keywords looks as below

   Mouse Over "HTML element ID 1"
   Click Link "HTML element ID 2"

   when we try this "Mouse over" keyword is pass and success.
   we can also observe a mouse overing action on the HTML element with ID1. Robot framework is doing this fine.
   But we are facing an issue with "click link" as below:
   INFO Clicking link 'XXXXXXX'.
   FAIL WebDriverException: Message: u'Element is not clickable at point (-12789, 222.5)'

   so finally the point what i would like to convey is when i am trying to click on link following mouse over then only we are getting an issue with click link.
   if we are trying the same click link keyword alone on another HTML elements which doesn't require any mouse over then the click link keyword is success.

   So we guess the problem is with mouse overing, but we are not sure, we need u r expert suggestion :-)

   strange thing is........
   when we are running the same scripts we are getting this problem only for chrome,
   for the same scripts we are not getting this error in IE and FF.
   In IE and FF these same keywords are working fine in combination and is success.

   Please provide u r suggestions...
3. emanlove commented on Oct 11, 2012

   

   emanlove

   on Oct 11, 2012

   Member

   More actions

   @srib4ufrnd: Given your description that you have some AJAX actions which occur in series one after another and that your tests work on some systems and not others you could be experiencing some timing issues. You might try waiting between the hover and click. There are several ways to do this including several "Wait ..." commands within the Selenium2Library and some keywords within Robot Framework builtin libraries. Also note the "Timeouts" section under Introduction within the Selenium2Library keyword documentation.

   There is also implicit wait but I am debating with myself as to whether or not this will help. Implicit wait will check to see if an element is present and if not will poll for the element till it either finds it or times out. In you case the link seems to be there but the click location seems way off. So I am not sure if implicit wait in this case will say yes it is there before its position is really set. Personally I lean towards using implicit wait as it has saved me a few times when dealing with timing issues.

   Library  Selenium2Library  implicit_wait=3sec
   

   If you set implicit wait on library import do note it changes how tests check each time it tries to find and element but does not initially find it. So you can also try

   ${orig wait} =   Set Selenium Implicit Wait   3 seconds
   < Perform AJAX call that is slow ... >      
   Set Selenium Implicit Wait  ${orig wait}    
   
4. srib4ufrnd commented on Oct 15, 2012

   

   srib4ufrnd

   on Oct 15, 2012

   Author

   More actions

   Hi @emanlove
   Thanks for ur suggestion but the solution is not working for us :-(

   is there any way where we can say the "mouse over" keyword to stay on the same position for more time?
5. emanlove commented on Oct 19, 2012

   

   emanlove

   on Oct 19, 2012

   Member

   More actions

   @srib4ufrnd Do you have a test page you can share?
6. Vall0n commented on Dec 6, 2012

   

   Vall0n

   on Dec 6, 2012

   More actions

   Hi,

   I had a similiar problem. Maybe you can try the following:

   Mouse Over "HTML element ID 1"
   Focus "HTML element ID 1"
   Simulate "HTML element ID 2" click

   This workaround worked for me. Hope it Helps!

   Best regards,

   Vall0n
7. srib4ufrnd commented on Dec 7, 2012

   

   srib4ufrnd

   on Dec 7, 2012

   Author

   More actions

   Hi VallOn

   Thanks a lot for the reply,

   we have written our test as suggested by u and as below, but still no luck :-( we are using chrome.

   Mouse Over "HTML element ID 1"
   Focus "HTML element ID 1"
   Simulate "HTML element ID 2" Click Link

   For u r information
   The html element with id 2 is an tag which is inside a

8. tag
   • Html Element Id 1
     • Html Element Id 2

   finally we will have a web page which has 3 horizantal elements
   link1 link2 link3

   link3 (which has tag with id Html Element Id 1)is the one on which i have to mouse over which shows me a drop down list of two links again

         link4 (which has <a> tag with Html element Id 2) This is the link i need to click
   

   But the code we tried above is not working.

   can u tell me any thing extra u did or we any thing extra we need to take care?