search

rshf / chromedriver

Automatically exported from code.google.com/p/chromedriver
2 stars 1 forks source link

Implicit waits should also apply to WebElement manipulation preconditions #24

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
From http://code.google.com/p/selenium/issues/detail?id=711:

Consider:

    driver.manage().timeouts().implicitlyWait(3, TimeUnit.SECONDS);
    WebElement button = driver.findElement(By.id("my-button"));
    button.click();

If "button" is not present on the DOM, findElement() will wait up to 3 seconds 
for it to be added before throwing NoSuchElementException.

If "button" is not visible yet, click() will immediately throw an 
ElementNotVisibleException.

Implicit waits should be used to wait for:
- locating elements
- element UI manipulation preconditions (visible, enabled, etc.)

Original issue reported on code.google.com by kkania@chromium.org on 5 Mar 2012 at 10:02

GoogleCodeExporter commented 9 years ago 
Issue chromium:87673 has been merged into this issue.

Original comment by kkania@chromium.org on 5 Mar 2012 at 10:02

GoogleCodeExporter commented 9 years ago

Original comment by kkania@chromium.org on 13 Mar 2013 at 11:55

GoogleCodeExporter commented 9 years ago

Original comment by kkania@chromium.org on 14 Mar 2013 at 9:20

GoogleCodeExporter commented 9 years ago

Original comment by kkania@chromium.org on 14 Mar 2013 at 9:21

GoogleCodeExporter commented 9 years ago

Original comment by kka...@google.com on 31 May 2013 at 12:15

GoogleCodeExporter commented 9 years ago 
Reopening. The test in the following thread throws an 
ElementNotVisibleException when calling click().

https://groups.google.com/forum/#!topic/chromedriver-users/udvINLk-34Q

Original comment by samu...@chromium.org on 26 Nov 2013 at 5:30

GoogleCodeExporter commented 9 years ago

Original comment by kka...@google.com on 13 Jan 2014 at 6:16

GoogleCodeExporter commented 9 years ago

Original comment by samu...@chromium.org on 21 Feb 2015 at 12:19