Actual Window Manager [new] May 2026
Thus, the "actual window manager" is not a neutral piece of infrastructure. It is an opinionated choreographer of human attention. If we dig deeper than the compositor, past the input router, beyond the policy engine, we find the kernel and the display server .
The actual handoff is precise: the window manager routes the event to the correct process based on its internal map. But the map is always slightly out of date. Because your input arrives asynchronously—interrupts, device drivers, kernel queues, compositor scheduling—the window manager must guess which window is actually under the cursor at the moment of click, not when the event was recorded.
Notice a pattern: the window manager is never just a manager. It is a compositor, an input router, a focus policy arbiter, and often a renderer for window borders and decorations. The pure, Platonic "window manager"—a module that only manages rectangles—exists only in textbooks and minimalist X11 setups from 1998. Part IV: The Input Gap Let us perform a small experiment in your mind. actual window manager
This is the deepest truth:
| System | What You Call It | What It Actually Is | |--------|------------------|----------------------| | Windows 11 | Desktop Window Manager (DWM) | A compositor + policy engine + input router, tightly coupled to the graphics kernel | | macOS | Quartz Compositor (part of WindowServer) | A userspace compositor + event manager + window database | | Linux (GNOME) | Mutter | A Wayland compositor + window manager + input manager | | Linux (KDE) | KWin | The same, but with pluggable window decoration and tiling scripts | | Linux (i3/sway) | i3 or Sway | A tiling window manager that is also a compositor (Sway) or relies on X11 (i3) | Thus, the "actual window manager" is not a
Now move the mouse to a text field in your browser. Click again. This time, the browser receives the click, moves its own cursor, and starts blinking.
Your text editor draws to a hidden buffer. Your browser draws to another. The compositor steals both, layers them, and presents a photograph of windows to the display. When you drag a window, you are not moving the window—you are moving the photograph of a window, then asking the application to redraw its hidden canvas, then taking a new photograph. The actual handoff is precise: the window manager
On a "click-to-focus" system, the window under your mouse receives keyboard input. On a "focus-follows-mouse" system, moving the mouse into a window brings it forward and grants it input. On a "sloppy focus" system, focus moves with the mouse but does not raise the window. On a tiling window manager, focus is often bound to the currently selected container.
