Question

59

Selenium JavaScript executor returning null when JS works fine on Chrome console

rated 0 times [ 65] [ 6] / answers: 1 / hits: 6396 / 11 Years ago, tue, december 10, 2013, 12:00:00

I'm trying to add some text to a text box in an iframe using Selenium + ChromeDriver (Java-driven) and I'm getting the following error in my stack trace:

org.openqa.selenium.WebDriverException: unknown error: Cannot read property 'contentWindow' of null

I've used a breakpoint to ensure the entire DOM is loaded so that doesn't appear to be the issue. I've also tested my JS in the Chrome console while at the breakpoint on the js.executeScript line and it works fine. As soon as I step forward through my test, though, it fails with the same error. It appears to be some discrepancy between how the JS is being run through Selenium as opposed to how it is being run through Chrome's console.

Here is the part of the DOM I'm looking at:

<div class=container>

 <iframe class=rich-text-area id=EmailMessage>

  #document

   <html>

    <head>

     <link rel=stylesheet type=text/css href=/static/css/rich-text-editor.css>

     <link rel=stylesheet type=text/css href=/rest/email/css>

     </head>

     <body contenteditable=true></body>

   </html>

 </iframe>

 <textarea class=code aria-hidden=true id=emailSource style=display: none;>            </textarea>

</div>

When running my JS in the Chrome console which is:

document.getElementById('EmailMessage').contentWindow.document.body.appendChild(document.createTextNode('testText'));

I get the desired result which is inner HTML between the body tags as such:

<body contenteditable=true>testText</body>

However, when running it using the following code, it's blowing up and giving me the error noted above. Here is the part of my Java code that runs this:

JavascriptExecutor js = (JavascriptExecutor) driver;

driver.switchTo().frame(emailBodyID);

wait.until(ExpectedConditions.visibilityOfElementLocated(emailBodyTag));

wait.until(ExpectedConditions.elementToBeClickable(emailBodyTag));

js.executeScript(document.getElementById('EmailMessage').contentWindow.document.body.appendChild(document.createTextNode('testText')););

driver.switchTo().defaultContent();

Any idea what's going on here? I've tried contentDocument.body as well. Same results in Chrome and Selenium. I'm using this as an alternative to sendKeys() as I'm forced to run an older version of ChromeDriver for this test that has broken support for sendKeys() in iframes. I've tried this code on my local machine with the latest ChromeDriver and it's still failing so it doesn't appear to be an environmental issue.

Cheers,
Darwin.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

jocelynkarsynr

Add To Favorites

Follow

Total Points: 472

Total Questions: 98

Total Answers: 96

Location: Macau

Member since Mon, Nov 16, 2020

4 Years ago

jocelynkarsynr questions

1 file upload using axios in react

Tue, Feb 8, 22, 00:00, 2 Years ago

1 Unable to write data (addRow) into Excel file in Nodejs

Sat, Jul 11, 20, 00:00, 4 Years ago

1 How can I export * as namespace in Babel?

Sun, May 10, 20, 00:00, 4 Years ago

1 React Routing to Same Component with Different URL

Sat, Jan 18, 20, 00:00, 4 Years ago

1 How do I persist user authentication using the Firebase refresh token?

Tue, Aug 20, 19, 00:00, 5 Years ago

View All

answered 11 Years ago everardo · Accepted Answer

Looks like I've found the answer to this after some more investigation. The issue was with the driver.switchTo() commands. The Chrome console was interpreting the code on the default page level where Selenium was looking at the DOM only from 'EmailMessage' up. These were left in there as a result of previously using SendKeys().

Reordering the lines to the following allowed the elements in the iframe to be checked with their explicit waits and then the JS to be run on the page level. Another solution would be to change the JS string to begin at the document.body... level. My fix is as follows:

JavascriptExecutor js = (JavascriptExecutor) driver;

driver.switchTo().frame(emailBodyID);

wait.until(ExpectedConditions.visibilityOfElementLocated(emailBodyTag));

wait.until(ExpectedConditions.elementToBeClickable(emailBodyTag));

driver.switchTo().defaultContent();

js.executeScript(document.getElementById('EmailMessage').contentWindow.document.body.appendChild(document.createTextNode('testText')););

Fairly simple and a bit obvious looking back at it (isn't everything though), but for anyone wanting to switch SendKeys() with some JS in an iframe (or perform any other action involving JS and changing scopes with iframes in Selenium), it's something that can be a bit of sneaky issue.