dacat / sfapi

Automatically exported from code.google.com/p/sfapi
0 stars 0 forks source link

Trying to click button fails when the button has been previously disabled and then enabled #31

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I have .mxml-file, where the button is created and where the enabled
property is set "false". In the application when the user checks a checkbox
the flex-script changes the button enabled property to be "true".

It seems that Flex selenium sees that the button is still disabled, even if
a real user could click the button. So the "click()"-method doesn't do
anything. 

Click() works fine on other buttons which have always been enabled.

Original issue reported on code.google.com by Vepsus...@gmail.com on 3 Jun 2010 at 6:13

GoogleCodeExporter commented 9 years ago
Sorry, my issue isn't really a issue or at least the problem is elsewhere. 

It seems that when there are two objects with the same ID, the click -method 
clicks the one which is in the background (for example, if I have a popup with 
"saveButton" and behind it there is a page with another "saveButton", it tries 
to press the second one -> not wanted behaviour)

Original comment by Vepsus...@gmail.com on 14 Jun 2010 at 1:59

GoogleCodeExporter commented 9 years ago
Did you try putting the parent or even grant parent id before the id you want? 
For example, parentId/saveButtonId, so that it will be different than another 
saveButton somewhere else.

Original comment by yugan...@gmail.com on 13 Jul 2010 at 7:50