The chrome on my office Mac machine recently updated to 76+. Since then one of the tests, written in Protractor and CucumberJS, started failing to cite this error -

WebDriverError: unknown error: failed to parse value of getElementRegion
     (Session info: chrome=76.0.3809.87)

I managed to fix the error since the element in the DOM was actually changed by the FE developer (on the same day the update occurred) and changing the locator fixed the test case. However, I'm curious why I got this error and not ElementNotFoundException or NoSuchElementException instead.

Googling this doesn't result in a lot of answers and as to what this error actually refers to. The only links that I got were from the ChromeDriver code, and it appears in line 587 here -


A similar question asked on SO a couple of years back has no answers - here

Looking to get more answers from the community around this error and what is the cases when this error should come.

  • I've gotten that error using selenium-standalone, then I gone for webdriver-manager and everything gone well. Aug 7, 2019 at 15:04
  • Where is the stacktrace? Virtually there is no information provided on the element which caused this issue in the first place. Aug 8, 2019 at 16:33

2 Answers 2


I had the same problem, and solved it by deleting the line SELENIUM_PROMISE_MANAGER: false in my conf.js file on my protractor configuration.

  • 3
    An explanation of why this worked would make this answer more useful.
    – c32hedge
    Aug 12, 2019 at 16:55

For me this Error occured because I was not accessing the real element, but it's shadow DOM instance instead. The element exists, thus no NoSuchElementException but it is not visible. Resolve this by using $$(YOUR_SELECTOR).get(INDEX_OF_REAL_ELEMENT)

  • Just a note that I encountered the "driver failed to parse value of getElementRegion" under similar circumstances. I was using a selector that matched both what I wanted (an h1) and, unexpectedly, the header's title element. I fixed the selector to match only the h1 and the error went away.
    – asmecher
    Dec 4, 2019 at 21:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.