---
title: "Button click does nothing: find where the click stopped | Proofline"
description: "When a button does nothing, check the Network panel first. A click that sent a request points at the response."
url: https://proofline.sh/learn/button-click-does-nothing/
---

[Learning center](/learn/)

# Button click does nothing: find where the click stopped

When a button does nothing, check the Network panel first. A click that sent a request points at the response. A click that sent none points at the page: either the click never reached the handler, or the handler stopped before its request. A click breakpoint and three Console checks then place the failure.

Network outages The Proofline team November 20, 2026 5 min read

## Two causes that look the same

A dead button looks identical whether the click never reached the code or the code ran and failed quietly. The fixes are in different places.

|  | Cause A: the click never ran the handler | Cause B: the handler ran and its work failed |
| --- | --- | --- |
| Network panel | No new request when you click | A new request with an error status or an unexpected body, or no request when the handler threw or returned before sending it |
| Click listener breakpoint | Never pauses in the handler | Pauses in the handler |
| Typical reasons | An invisible element covers the button, the button is disabled, or the script that attaches the handler failed to load | The handler threw or returned early, the server rejected the request, or the page ignored the error response |
| Where the fix goes | Markup, styles or script loading | The handler's error path, or the server |

Start with whether a request appears in the Network panel at the moment you click. Clear the list, turn on **Preserve log**, click once and look. A request means the handler ran. No request does not yet mean it never ran, so the deciding observation is whether a click breakpoint pauses in the handler. [Network panel reference](https://developer.chrome.com/docs/devtools/network/reference)

## If no request appears

First find out whether the handler ran. Open **Sources**, expand **Event Listener Breakpoints**, tick **Mouse > click** and click the button. For a submit button, also tick **Control > submit**, because a form's `submit` listener runs as a separate event that a click breakpoint does not catch. DevTools pauses in the first listener that runs. [Event listener breakpoints](https://developer.chrome.com/docs/devtools/javascript/breakpoints)

With a framework that attaches one listener at the root, DevTools first pauses in the framework's code; step into its calls until you reach the button's own handler. If it pauses in the button's or the form's handler, the click worked and the handler stopped before its request: Cause B. Step through it until it returns or throws. Also tick **Pause on uncaught exceptions** and **Pause on caught exceptions**, because a handler that catches its own error and does nothing shows no Console message. The line where it returns or throws goes in the report.

If it never pauses, or pauses only in another element's listener, the click never reached the handler: Cause A. Three checks place the problem in order of how often they explain it.

**Is something on top of the button?** Cookie banners, transparent overlays and modal backdrops can sit over a button and take the click. In the Console, ask the browser which element is at the button's centre:

```
const r = $0.getBoundingClientRect();
document.elementFromPoint(r.x + r.width / 2, r.y + r.height / 2);
```

Select the button in the Elements panel first, so `$0` refers to it. If the result is not the button or one of its children, the click lands on that element instead. [`elementFromPoint`](https://developer.mozilla.org/en-US/docs/Web/API/Document/elementFromPoint) · [Console utilities](https://developer.chrome.com/docs/devtools/console/utilities)

**Is a click listener attached?** With the button selected, run `getEventListeners($0)` in the Console, or open the **Event Listeners** tab in the Elements panel. Frameworks often attach one listener at the root instead of on each button, so also check the ancestors. An empty result on the button and every ancestor means the code that should attach it never ran. [Console utilities](https://developer.chrome.com/docs/devtools/console/utilities)

**Did a script fail before the handler was attached?** Reload with the Console open. An uncaught error during page load, or a script request with `404` in the Network panel, can stop the code that attaches the handler. The button renders from HTML and does nothing.

## If a request appears

The click worked; the response did not produce a visible result. Select the request and read its status and Response tab. Then look at the Console at the same moment. A `4xx` or `5xx` that the page did not display means the handler lacks an error path. A `200` with an unexpected body, followed by a console exception, means the handler failed while reading the response.

If the request shows `CORS error` or a status in parentheses, the guides on [CORS errors](/learn/cors-error-or-server-error/) and [requests with no status](/learn/failed-request-no-status/) continue from there.

## Worked example: Save behind a cookie banner

This example is fictional and reproduced in a local page with Chromium. A settings page has a **Save** button fixed near the bottom of the window. A cookie banner, 120 pixels tall and almost transparent, sits across the bottom of the window. A user reports that Save does nothing on a laptop but works on a large monitor.

Clicking Save sent no request, and the click breakpoint never paused in Save's handler. The Event Listeners tab showed a `click` listener on the button, so the handler existed. `document.elementFromPoint` at the button's centre returned `DIV#cookie`. On the large monitor, the button sat above the banner.

The report could then say: _on a 768-pixel-tall window, the cookie banner covers Save, and clicks land on the banner. No request is sent. The button's click listener is attached._ That sends the fix to layout, not to the settings API.

## What to put in the report

-   Whether a request appeared on click, with its method, URL and status if it did.
-   Whether the click breakpoint paused in the handler, and if so where the handler returned or threw.
-   The result of `elementFromPoint` at the button, and whether a listener is attached.
-   Any console error during page load or at the click.
-   The window size and zoom level, since covered buttons often depend on them.
-   What you could not check, such as whether the server received anything.

## Questions

### The button works when I click it a second time. Why?

The first click may land on an overlay that closes on click, or the handler may be attached late, after a slow script loads. Record how long after page load the first click happened, and whether the Network panel showed a script still loading.

### Can a disabled button still look enabled?

Yes. Styling can make a disabled button look active. In the Elements panel, check for the `disabled` attribute and for `pointer-events: none` in the Computed styles. [`pointer-events`](https://developer.mozilla.org/en-US/docs/Web/CSS/pointer-events)

### Does this apply to links and form submits?

Yes. A link or submit button that does nothing has the same two causes. A form submit may also be stopped by validation: look for an invalid field, which the browser marks with a message near the field. [Constraint validation](https://developer.mozilla.org/en-US/docs/Web/HTML/Guides/Constraint_validation)

Return to the [method for browser bug reports](/learn/browser-bug-report-evidence/) for the other symptoms in this collection.

## One month of free code review.

New organizations get one calendar month of hosted code review for private and public GitHub repositories. No card or cloud connection required. [Eligibility and fair-use terms](/free-code-review/).

[Start free with GitHub](https://proofline.sh/orgs/plan?offer=free_month)

## Related reading

-   ### [Turn a browser symptom into a bug report another engineer can act on](/learn/browser-bug-report-evidence/)
    
    Network outages The Proofline team November 20, 2026 7 min read
    
-   ### [A request with no status code: read (failed), (canceled) and (blocked)](/learn/failed-request-no-status/)
    
    Network outages The Proofline team November 20, 2026 4 min read
