aboutsummaryrefslogtreecommitdiff
path: root/CHANGELOG.md
diff options
context:
space:
mode:
authorDaniel Eklöf <daniel@ekloef.se>2026-01-04 06:57:25 +0000
committerDaniel Eklöf <daniel@ekloef.se>2026-01-04 17:59:20 +0000
commitb78cc92322dd2ae431dbbb70bc681b4d603d844d (patch)
treee7b412b09a1bad2a2917770a774015af641d9f90 /CHANGELOG.md
parentcsi: secondary DA: fix comment; we don't use an XTerm version number (diff)
shm: don't bother with xrgb surfaces, always use argb
Before this patch, foot used xrgb surfaces for all fully opaque surfaces, and only used argb surfaces for the main window when the user enabled translucency. However, several compositors have damage-like issues when we switch between opaque and non-opaque surfaces (for example, when switching color theme, or when toggling fullscreen). Since the performance benefit of using non-alpha aware surfaces are likely minor (if there's any measurable performance difference at all!), lets workaround these compositor issues by always using argb surfaces.
Diffstat (limited to 'CHANGELOG.md')
-rw-r--r--CHANGELOG.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 6fa7439e..0462666c 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -92,6 +92,11 @@
contains at least one upper case character.
* Mouse tracking in SGR pixel mode no longer emits negative column/row
pixel values ([#2226][2226]).
+* Foot now always uses ARGB SHM surfaces. In earlier versions, XRGB
+ surfaces were used for opaque surfaces. Unfortunately, several
+ compositors had issues when foot switched between ARGB and XRGB
+ surfaces (for example when switching color theme, or toggling
+ fullscreen).
[2202]: https://codeberg.org/dnkl/foot/issues/2202
[2226]: https://codeberg.org/dnkl/foot/issues/2226