Skip to content

Conversation

@TikhomirovSergey
Copy link
Contributor

#110 Fix.

Now it is possible to change timeout of the implicit waiting for element is present for already instantiated proxy of WebElement.

Raw example:

public class MyScreen_PageObject{

@FindBy annotation with locator value
WebElement field;

//staff
AppiumFieldDecorator afd = new AppiumFieldDecorator(driver);
PageFactory.initElements(afd, this);
//staff

public void clickOnField(){
  afd.resetImplicitlyWaitTimeOut(2, TimeUnit.SECONDS);
  //It will wait for element is present for 2 seconds.
  field.click();
}

I think this feature is good for some common situations and it would be great when Spring or CGLIB are used.

@bootstraponline
Copy link
Member

How is this related to #100? As discussed at Selenium Conf 2014 implicit waits are a crutch and you should be using explicit waits. Modifying the wait time isn't a solution to finding incorrect elements.

@TikhomirovSergey
Copy link
Contributor Author

Opps! It is mistake!

@TikhomirovSergey TikhomirovSergey changed the title #100 Fix #110 Fix Sep 25, 2014
@TikhomirovSergey
Copy link
Contributor Author

#110

@bootstraponline
Copy link
Member

cool. It makes sense now.

@Jonahss Jonahss merged commit edbcbee into appium:interfacesRefactor Sep 25, 2014
@TikhomirovSergey TikhomirovSergey deleted the interfacesRefactor branch September 26, 2014 07:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants