Closed GoogleCodeExporter closed 9 years ago
please help me i am stuck
Original comment by prabji...@gmail.com
on 12 May 2014 at 1:20
Thanks for reporting this. Would it be possible for you to share an app that
exhibits this issue?
Original comment by renasr...@gmail.com
on 12 May 2014 at 3:52
cannot share the code but i will explain you on the webpage there is one
spinner now i want to click the spinner select the value and move to next page
for clicking the spinner i using
solo.clickOnWebElement(By.xpath("//div[@id\='surveyquescontent']/span[2]/select/
option[4]"));
i have also tried solo.clickOnWebElement(By.className("mrDropdown"));
solo.clickOnWebElement(By.id("_Q0_C"), 0, true);
Original comment by prabji...@gmail.com
on 13 May 2014 at 5:23
Please try to set config to: conf.useJavaScriptToClickWebElements = true.
Please see the javaodoc for more information.
Original comment by renasr...@gmail.com
on 8 Jun 2014 at 2:07
Config config = new Config();
config.useJavaScriptToClickWebElements = true;
config.screenshotFileType = ScreenshotFileType.PNG;
config.screenshotSavePath = Environment.getExternalStorageDirectory()
+ "/Robotium/";
config.shouldScroll = true;
solo = new Solo(getInstrumentation(), config, getActivity());
already added this line but still not working
i Have
Original comment by prabji...@gmail.com
on 9 Jun 2014 at 10:11
Can you share an app that exhibits this issue? A simple test app is enough.
Original comment by renasr...@gmail.com
on 9 Jun 2014 at 10:12
ok i will try....
Original comment by prabji...@gmail.com
on 9 Jun 2014 at 10:13
I am also having the same issue. I have used the click method on other objects
suck as buttons, text boxes and other things. The main issue is with spinners I
have tried to identify them using name/id and xpath. I think that the problem
could be when you click on the spinner itself the type is called select-one
which implies that it is a html element. However on android it becomes a
spinner.
Original comment by bsztu...@epitiro.com
on 21 Jul 2014 at 2:44
Original issue reported on code.google.com by
prabji...@gmail.com
on 12 May 2014 at 11:43