Ugh
Have you used Firebug [1], or similar tool, to verify the number of matching elements? Because Selenium2library is designed to take the first matching element from the DOM tree and interact with that element.
Because if you say that you can see and click the elements but the element is hidden from the html code, then you are looking/referring to the wrong element or something very weird is going on. In any case consulting your developer is a good idea. Because sometimes the DOM tree can be quite messy to read and understand.
-Tatu
[1] http://getfirebug.com
--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-u...@googlegroups.com.
To post to this group, send email to robotframe...@googlegroups.com.
Visit this group at http://groups.google.com/group/robotframework-users.
For more options, visit https://groups.google.com/groups/opt_out.
Ugh
Have you used Firebug [1], or similar tool, to verify the number of matching elements? Because Selenium2library is designed to take the first matching element from the DOM tree and interact with that element.
Because if you say that you can see and click the elements but the element is hidden from the html code, then you are looking/referring to the wrong element or something very weird is going on. In any case consulting your developer is a good idea. Because sometimes the DOM tree can be quite messy to read and understand.
-Tatu
[1] http://getfirebug.com
On 17 Jan 2014 06:36, "Lane" <nkc24...@gmail.com> wrote:
I can use mouse to click this checkbox, but still show hidden in html code.--I have use sleep to make sure page is displayed when run robot.This html code is our design by our produce. Is not this html code is design wrong? I can tell our engineers to modify this code, but if automation can do, this code will not need to be modify.
Kevin O.於 2014年1月17日星期五UTC+8上午11時45分47秒寫道:As a user, you cannot interact with hidden elements. WebDriver refuses to do so because it is trying to be a realistic test tool.Whatever you have to do to get the element to become visible as a human with a mouse, you will have to do the same in the automation. Sometimes the automation is to fast, so the Wait Until Element Is Visible keyword may help there.
You received this message because you are subscribed to the Google Groups "robotframework-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-users+unsub...@googlegroups.com.