Skip to content

Commit 43888d5

Browse files
committed
changelog: the prefer-no-csd bullet rides under 44.7.0
1 parent 6a61a3a commit 43888d5

1 file changed

Lines changed: 6 additions & 15 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 6 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,6 @@
22

33
## Unreleased
44

5-
- **Chromium apps stop painting their own titlebars.** `prefer-no-csd`
6-
joins the image's niri config: niri draws no titlebars, so when an
7-
app like Spotify (CEF) answers the decoration request by supplying
8-
its own, the result was a hardcoded blue client-side bar on every
9-
window. Refusing the CSD offer leaves the frame to the compositor,
10-
which draws none.
11-
125
## v44.7.0 (2026-10-10)
136

147
- **The session answers its own privileged prompts.** kuma-shell registers
@@ -93,14 +86,12 @@
9386
Network section always shows), and a markdown table with a multibyte
9487
cell no longer crashes the preview.
9588

96-
- **Negotiating windows shed their client-drawn titlebar.** The image's
97-
niri config now carries `prefer-no-csd`. Chromium/CEF and Electron apps
98-
drew their own titlebar on Wayland in Chromium's hardcoded default blue
99-
(rgb(93, 141, 218), measured on a Spotify flatpak), because the GTK
100-
theme never feeds the frame there, and niri renders no titlebars for
101-
windows that hand the job back. Apps that comply render bare under the
102-
Kuma look's ring and rounding; apps that insist on CSD keep their
103-
headerbars.
89+
- **Chromium apps stop painting their own titlebars.** `prefer-no-csd`
90+
joins the image's niri config: niri draws no titlebars, so when an
91+
app like Spotify (CEF) answers the decoration request by supplying
92+
its own, the result was a hardcoded blue client-side bar on every
93+
window. Refusing the CSD offer leaves the frame to the compositor,
94+
which draws none.
10495

10596

10697
## v44.6.0 (2026-10-09)

0 commit comments

Comments
 (0)