Why you have to click twice on a Mac

Updated 2026-09-12 · 5 min read · by Okie Dockie

What is actually happening

macOS separates two ideas that feel like one. Focus decides which window receives your typing and clicking. Activation is the act of giving a window that focus. When you click a window that is not currently in front, the click is consumed by activation: the window comes forward, and nothing else happens. Your second click is the first one the application actually sees.

It is a deliberate design, meant to stop you triggering something by accident in a window you were only trying to look at. It works well when you have two or three windows and badly when you have eight.

Why some clicks do work first time

Applications can opt into "click-through" for individual controls, and many do — inconsistently. A scroll bar in a background window usually works on the first click. A button next to it often does not. Finder allows some first-click actions; most apps do not.

This unpredictability is the real cost. You cannot build a habit around a rule that changes from control to control, so you end up clicking twice on everything out of caution, even when once would have done.

Why Windows and Linux feel different

Windows passes the click through to the control in almost every case: clicking a background window both focuses it and presses what is under the pointer. Most Linux desktops go further and offer focus-follows-mouse, where the window under the pointer receives keystrokes with no click at all.

Neither is objectively right. But if you have spent years on Windows, the Mac's behaviour registers as an unexplained delay dozens of times a day.

How to fix it

macOS ships no system-wide setting for this. The one built-in exception is Terminal:

defaults write com.apple.terminal FocusFollowsMouse -bool true

That affects Terminal and nothing else. Older tricks that poked at the window server stopped working as Apple tightened what unsigned code may do to other applications. Anything that works today does so through the macOS Accessibility API, with your explicit permission.

Okie Dockie uses that route: turn on click-through focus and the window under your pointer takes your keystrokes, so a click lands on the control you aimed at instead of being spent on focusing. It is part of the free version.

The part that goes wrong in most tools

Here is the detail that decides whether you keep the feature or switch it off after a day. Focusing a window and raising it are different things.

• Focus — which window gets your input.
• Raise — which window is visually on top.

You want focus. If hovering also raises, then every time your pointer crosses a window on its way somewhere else, that window jumps to the front and rearranges your screen. Drag the mouse diagonally across four tiled windows and you have reshuffled the stack four times. That is why most people who try focus-follows-mouse turn it off again.

Focusing without raising needs a specific, undocumented window-server call, and the obvious version of that call is the raising one. Okie Dockie deliberately offers no raise option: hover a window, type into it, click into it — the stacking order never changes.

One honest exception: Chromium browsers ignore a focus change that does not reorder windows, so moving between two Chrome windows still needs a click. Any tool that claims otherwise is raising windows, and you will notice.