invalid element state: Element is not currently interactable and may not be manipulated

[lukeis]

Originally reported on Google Code with ID 7723

I have this issue with selenium i can not find i textinput : it alwayes rases this exeception:
Element is not currently interactable and may not be manipulated

in this ligne : Driver.FindElement(By.Id("ctl00")).Clear();

i try to put waiting like this:

Waiting.Until(driver =>(By.Id("ctl00"))); and
Waiting.Until(ExpectedConditions.ElementExists(By.Id("ctl00"))); but no luck thanks

Kais

Reported by kais.zwawi@lunabee.com on 2014-08-07 08:15:19

[lukeis]

Selenium is finding the element - it's the Clear() command that's failing due to the
element being in an invalid state (e.g. <input readonly>).

Can't say more without a reproducible test case with HTML, CSS, and JS for the relevant
site.

Reported by jmleyba on 2014-08-07 16:59:55

• Status changed: NeedsClarification

[lukeis]

We are also facing with this issue. In our case it happens from time to time and very
dificult to debug it. One more comment: this issue occures in Jenkins. We use Selenium
WebDriver 2.24.2 + Selenium GRID 2.24.2.

Reported by cyril.dragomyr on 2014-08-19 06:49:14

[lukeis]

Closing the issue as there is no reproduction case provided.

Reported by barancev on 2014-09-15 02:48:00

• Status changed: Invalid

[lukeis]

I am doing the following:
 WebElement element = d().findElement( By.id("billing:city"));
        element.clear();
        element.sendKeys(city);
        element.sendKeys(Keys.TAB);

in line: element.clear()

org.openqa.selenium.InvalidElementStateException: invalid element state: Element is
not currently interactable and may not be manipulated.

(Session info: chrome=37.0.2062.124)
(Driver info: chromedriver=2.9.248315,platform=Windows NT 6.1 SP1 x86_64)

Reported by adriana.spreadshirt on 2014-09-29 15:44:52

[lukeis]

I have had this message from a input type text in chrome when isDisplayed=false, which
is basically due to some earlier part of the test not working.

Reported by kristian.rosenvold on 2014-10-21 09:05:58

[lukeis]

I have the same issue in the element.clear(), same as well Adriana.  When I use the
Firefox Driver, this problem dont't occur. When I debugg step by step.....neither occur.
  The problem is peculiar, but I dont find de bug. This case in Firefox occur but my
slution was put on in my code ImplicityWait, but in Chrome this dont work.

(Session info: chrome=39.0.2171.65)
  (Driver info: chromedriver=2.9.248315,platform=Windows NT 6.1 SP1 x86_64) (WARNING:
The server did not provide any stacktrace information)

Reported by Zidboy on 2014-12-03 12:39:13

[lukeis]

I found the problem, but I don´t now how fix it.
The problem is element.clear() but in some cases, because in other runs smoothly.

My test was comment the line and test runs whitout problems, but in this point my problem
is a very big, because my test is multi browser then in the some browsers runs whitout
problem and the other with problem.

I am very stressed with this problem, because don't found the solution to multibrowser.

Any comments? or any suggestions??

Reported by Zidboy on 2014-12-03 12:56:31

[lukeis]

I have the same issue with selenium i can not find i textinput : it alwayes rases this
exeception: Element is not currently interactable and may not be manipulated  


or Element is not currently visible and so may not be interacted with
Command duration or timeout: 60.04 seconds

can any body help me pls.......

Reported by lavanya.kotam on 2015-03-03 09:34:27

[lukeis]

In my case the problem was caused by element.clear() when used with chrome browser.

Reported by tteksoy on 2015-04-02 06:53:28