Client-Side Decoration¶
Assign an application client responsibility for rendering its own non-content window frame while coordinating move, resize, state, focus, and decoration mode with the window manager or compositor.
Core Idea¶
Client-side decoration assigns a graphical application responsibility for drawing the window frame around its content—commonly the title/header bar, border, shadows, and window controls—rather than having the window manager or compositor draw that frame. The window-management authority is not thereby abolished: the client must still request move, resize, maximize, minimize, and close behavior through the window-system protocol.
Wayland's xdg-decoration extension makes the split explicit by negotiating client-side or server-side mode between a toplevel client and compositor. GTK's header-bar component exemplifies a client-rendered surface that can combine title, controls, and application actions.
Scope of Application¶
CSD appears in Wayland and X11 desktop applications, GTK header bars, frameless Electron windows, and operating-system APIs for custom title bars. Microsoft's title-bar customization contract preserves system interaction behaviors while allowing application content in the title region. AppKit likewise exposes window style, title visibility, and movable regions through NSWindow.
Clarity¶
Specify which party draws each pixel, owns shadows, performs hit testing, supplies window buttons, and initiates move/resize operations. State protocol and compositor support, fallback mode, accessibility representation, scale-factor handling, focus styling, and behavior when the client stalls.
Manages Complexity¶
The technique lets application chrome and window chrome share one layout, reclaim unused title-bar space, and adapt to narrow form factors. It also moves cross-desktop consistency, input hitboxes, and some reliability obligations into each toolkit or application.
Abstract Reasoning¶
- Negotiate or detect the permitted decoration mode.
- Reserve a client-rendered frame region outside or above primary content.
- Draw title, state, actions, and controls using current scale and theme.
- Mark draggable and resizable regions without stealing ordinary widget input.
- Translate control activation into window-protocol requests.
- React to focus, maximization, tiling, fullscreen, and capability changes.
- Expose controls and title semantics to accessibility services.
- Test compositor, toolkit, theme, scaling, and unresponsive-client failure cases.
Knowledge Transfer¶
The portable pattern is move presentation responsibility to the component with application context while retaining state-changing authority at the system boundary. It transfers to embedded editors and custom media controls. The proposed immediate parent is Delegation of Authority.
Relationships to Other Abstractions¶
Current abstraction Client-Side Decoration Domain-specific
Parents (1) — more general patterns this builds on
-
Client-Side Decoration is a kind of Delegation of Authority Prime
Delegation of Authority is the proposed immediate parent.
Hierarchy path (1) — routes to 1 parentless root
- Client-Side Decoration → Delegation of Authority → Authority
Neighborhood in Abstraction Space¶
Client-Side Decoration sits in a sparse region of the domain-specific corpus (100th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Unclustered & Miscellaneous (1565 abstractions)
Nearest neighbors
- Interaction Flow Modeling Language — 0.77
- Virtual Desktop — 0.75
- Frame (GUI) — 0.73
- Non-local variable — 0.71
- Context-sensitive user interface — 0.71
Computed from structural-signature embeddings · 2026-09-08