Non-Interactable Elements

61 views
Skip to first unread message

David Czerwinski

unread,
Jun 8, 2024, 4:16:58 AM6/8/24
to Selenium Users
So I'm writing a javascript selenium test and ran into a non-interactable element... I've tried all the locators and implicit / explicit waits inside try/catches but still can't seem to crack why this element is not interactable... How have you been able to identify the reason for elements not being interactable?

Adrian

unread,
Jun 11, 2024, 3:33:56 PM6/11/24
to Selenium Users
Hi,
The element may not be interactable because another element is sitting on top of the target element.  
Usually, the error message will indicate that situation.  It would say something like another element would receive the click.
If this is the case, then you will need to get a developer to move the overlapping element so that you can access the target element.

Cheers,
Adrian.

David Czerwinski

unread,
Jun 17, 2024, 3:36:13 PM6/17/24
to Selenium Users
I wish it was an issue with interception... this bug is much more vague and realized i should probably drop the error message in the thread lol

ElementNotInteractableError: element not interactable

(Session info: chrome=125.0.6422.142)
at Object.throwDecodedError (Path\To\Project\node_modules\selenium-webdriver\lib\error.js:522:15)
at parseHttpResponse (Path\To\Project\node_modules\selenium-webdriver\lib\http.js:589:13)
at Executor.execute (Path\To\Project\node_modules\selenium-webdriver\lib\http.js:514:28)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Driver.execute (Path\To\Project\node_modules\selenium-webdriver\lib\webdriver.js:740:17)
at Object.method (Path\To\Project\.js:50:5)
at function (Path\To\Project\.js:507:13)
at function (Path\To\Project\.js:1189:7)
at function (Path\To\Project\.js:1145:19)
at Object.method (Path\To\Project\.js:1126:29)
at Object.method (Path\To\Project\.js:17:22)
at Object.<anonymous> (Path\To\Project\.js:271:3)
at callCircusTest (Path\To\Project\nodemodules\jest-circus\build\run.js:212:5)
at runTest (Path\To\Project\nodemodules\jest-circus\build\run.js:149:3)
at runTestsForDescribeBlock (Path\To\Project\nodemodules\jest-circus\build\run.js:63:9)
at run (Path\To\Project\node_modules\jest-circus\build\run.js:25:3)
at runAndTransformResultsToJestFormat (Path\To\Project\node_modules\jest-circus\build\legacy-code-todo-rewrite\jestAdapterInit.js:176:21)
at jestAdapter (Path\To\Project\node_modules\jest-circus\build\legacy-code-todo-rewrite\jestAdapter.js:109:19)
at runTestInternal (Path\To\Project\node_modules\jest-runner\build\runTest.js:380:16)
at runTest (Path\To\Project\node_modules\jest-runner\build\runTest.js:472:34)
at Object.worker (Path\To\Project\node_modules\jest-runner\build\testWorker.js:133:12) {
remoteStacktrace: '\tGetHandleVerifier [0x00FAB793+45827]\n' +
'\t(No symbol) [0x00F3DB74]\n' +
'\t(No symbol) [0x00E3138D]\n' +
'\t(No symbol) [0x00E73074]\n' +
'\t(No symbol) [0x00E685EF]\n' +
'\t(No symbol) [0x00E92DFC]\n' +
'\t(No symbol) [0x00E68075]\n' +
'\t(No symbol) [0x00E93094]\n' +
'\t(No symbol) [0x00EAC034]\n' +
'\t(No symbol) [0x00E92B96]\n' +
'\t(No symbol) [0x00E66998]\n' +
'\t(No symbol) [0x00E6751D]\n' +
'\tGetHandleVerifier [0x012643C3+2899763]\n' +
'\tGetHandleVerifier [0x012B77ED+3240797]\n' +
'\tGetHandleVerifier [0x01031264+593364]\n' +
'\tGetHandleVerifier [0x0103818C+621820]\n' +
'\t(No symbol) [0x00F46F54]\n' +
'\t(No symbol) [0x00F43658]\n' +
'\t(No symbol) [0x00F437F7]\n' +
'\t(No symbol) [0x00F358AE]\n' +
'\tBaseThreadInitThunk [0x77367BA9+25]\n' +
'\tRtlInitializeExceptionChain [0x77C9BE3B+107]\n' +
'\tRtlClearBits [0x77C9BDBF+191]\n'
}


at function (path.js:514:21)
at runMicrotasks (<anonymous>)


Adrian

unread,
Jun 17, 2024, 4:12:54 PM6/17/24
to Selenium Users
Can you attach a copy of the DOM?
And highlight which element you are trying to interact with?

Cheers,
Adrian.

David Czerwinski

unread,
Jun 17, 2024, 7:19:58 PM6/17/24
to Selenium Users
WE GOT IT!

looks like there was an issue with the codebase! the map being used to render components wasn't filtering as expected but its working now :)

Adrian Tankard

unread,
Jun 17, 2024, 7:37:29 PM6/17/24
to seleniu...@googlegroups.com

That is good news!


--
You received this message because you are subscribed to a topic in the Google Groups "Selenium Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/selenium-users/b1JNGyfjs5U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to selenium-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/5e104781-d565-46cd-b0e9-9e573e330f63n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages