When Selenium reports “element is not clickable at point” or throws ElementClickInterceptedException, the browser could not direct its attempted click to the intended control at that location. First inspect the full exception—especially any element named as the click recipient—and the page as it looked when the test failed. An overlay, scroll or layout state, or a locator targeting the wrong control can explain the failure, but the message alone does not establish which cause applies.
What the exception means
WebDriver’s ordinary element click is intended to activate an element through the browser’s interaction path. If something else occupies the click location, the browser may report that the other element would receive the click. Newer exception wording commonly identifies this as ElementClickInterceptedException. The text “Element is not clickable at point” appears in reports and troubleshooting material, but exact wording can vary.
As an Amazon Associate I earn from qualifying purchases.
Do not assume this is simply a slow test. A wait can help if the page is still changing; it cannot remove a persistent banner or make an incorrect locator point to the intended visible control.
Diagnose the failure in order
- Read the complete exception. Look for the target element, coordinates, and any element named as the click recipient. If a dialog, consent banner, sticky header or footer, toast, or backdrop is named, inspect whether it covers the target.
- Reproduce and inspect the page at failure time. Capture a screenshot or inspect the DOM and computed visibility around the target and blocker. A screenshot can help preserve visual evidence; it does not alone identify the DOM element receiving the click.
- Confirm the locator identifies the intended visible control. Responsive pages can contain hidden desktop/mobile duplicates. Check the matched element’s visibility and enabled state, and verify that the locator is not selecting a hidden copy.
- Check whether the blocking UI is expected. If it is, perform the user-facing action that dismisses it or complete the preceding interaction. If it should disappear automatically, wait for that specific blocker to become invisible or be removed.
- Check scroll and layout. Determine whether the target is in the viewport and whether a sticky element or changing layout occupies its click location. Scroll it into a usable position if needed, then retry a normal WebDriver click.
- Retry only after the relevant condition is true. Prefer an explicit wait for the blocker to disappear or for the target to become ready over a fixed sleep. A delay cannot fix a permanent overlay or a wrong locator.
Fix the underlying page state
Dismiss an overlay before clicking
If the named click recipient is a consent banner, modal, or other intentional interface, automate the same dismissal or preceding action a user would take. Katalon’s exception-specific guidance says that when another object such as a pop-up dialog covers the target, the test can add actions to remove that object before clicking. This is Katalon guidance, not a universal Selenium guarantee; use the equivalent interaction in your test framework.
Wait for a transient blocker or a ready target
When an animation, toast, or loading state is temporary, wait for the condition that matters—for example, the blocker to become invisible, or the target to be visible and enabled—then click. A target being visible and enabled is useful but does not prove that no other element covers its click point, so inspect interception evidence as well.
Correct the locator or viewport
If the locator matches a hidden duplicate, scope it to the correct visible region or refine it to identify the intended control. If the target is obscured by a sticky header or footer, adjust the page state or scroll position and verify the click location before retrying. Do not switch to a different locator merely to silence the exception unless it identifies the control the test is meant to operate.
When JavaScript click is—and is not—a fix
A JavaScript call such as arguments[0].click() can activate an element through the DOM, and Katalon documents it as a workaround for click failures. It may bypass the browser hit-testing that caused a normal WebDriver click to be intercepted. That means the test can pass without proving that a user could click the control on screen.
#1 Best Overall
Use JavaScript activation only when DOM-level activation is explicitly what the test intends. For user-facing interaction tests, resolve the overlay, locator, readiness, or viewport problem and keep the ordinary WebDriver click. If you use the workaround, make the distinction visible in the test name or comments so it is not mistaken for proof of a successful user click.
Scroll failures: treat reports as version-specific
SeleniumHQ issue #16345 reports a failure to scroll fully into view in a specific reproduction using Selenium 4.35.0 Java bindings with Chrome/Chromium 140 and logs that also show Chrome 139. The reporter describes both headed and headless runs and says a larger viewport did not avoid the behavior. This is a version- and reproduction-specific issue report, not evidence that every Selenium/browser combination has a general scroll defect.
Rank #2
If your failure resembles that report, record the Selenium binding and version, browser and version, driver version, headless/headed mode, viewport, and page state. Then reproduce with your exact setup and check the issue for its current status before attributing the problem to Selenium itself.
Troubleshooting by symptom
| Symptom | What to check | Next step |
|---|---|---|
| The exception names a different element as the click recipient | Whether that element is a dialog, banner, sticky region, toast, or backdrop covering the target | Dismiss it through the intended interaction, or wait for a transient blocker to disappear. |
| The click fails intermittently during page transitions | Whether animation, loading, or a temporary overlay is still active | Wait for the specific ready condition or blocker state, not an arbitrary amount of time. |
| The locator finds more than one matching control | Whether one match is hidden or belongs to a responsive layout that is not active | Refine or scope the locator to the visible, intended control. |
| The target is off-screen or partly covered after scrolling | Its position relative to sticky headers/footers and the current viewport | Adjust scroll or page state, then retry an ordinary WebDriver click. |
| JavaScript click passes while WebDriver click fails | Whether the test is meant to verify a real on-screen interaction | Keep JavaScript only for an intentional DOM-level test; otherwise fix the obstruction or state. |
| The failure appears tied to one browser/version combination | Exact Selenium, browser, driver, viewport, and execution-mode versions | Reproduce and compare against the version-specific issue report rather than assuming a universal defect. |
Capture visual evidence without running a browser yourself
A screenshot taken at the right point in a test can help you see banners, overlays, and layout shifts. ScreenshotNeo is a website screenshot API and MCP server from Yorker Media; it is useful when you want a screenshot of a URL without setting up browser capture code in that workflow. It is not a substitute for inspecting the live Selenium session when the failure depends on that session’s cookies, authentication, or timing.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Or skip the browser setup:
One GET request can return a screenshot; the documentation is at https://screenshotneo.com/docs/.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpScreenshotNeo accepts cookie and consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots. See ScreenshotNeo for details, or sign up free for 1,000 screenshots a month with no card.
Frequently Asked Questions
Does “element is not clickable at point” always mean an overlay is present?
No. An overlay is a common explanation, especially when the exception names another click recipient, but inspect the page state and locator before deciding.
Should I replace every failed Selenium click with JavaScript?
No. JavaScript activation can bypass ordinary browser hit-testing and does not establish that a user could click the control. Use it only when DOM-level activation is the intended test.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
