Published event
DeveloperTools ProductUpdate 1 source(s)

LabWC real transparent blur ext-background-effect-v1

Updated October 4, 2026 · 12:05 AM · 23 · source date October 3, 2026

Summary

LabWC real transparent blur ext-background-effect-v1 labwc / labwc Public Notifications You must be signed in to change notification settings Fork 268 Star 2.8k Conversation grigio commented Oct 2, 2026 Copy link Copy Markdown Description Real transparency blur in terminal like alacritty, it implements Wayland ext-background-effect-v1 #3391 labwc-blur.mp4 How has it been tested? alacritty with blur Checklist The contribution does not contain any AI-generated content The contribution is consistent with our philosophy g added 3 commits October 3, 2026 01:52 Implement ext-background-effect-v1 3beefc5 Add support for the ext-background-effect-v1 protocol (wayland-protocols staging), discussed in labwc#3391 .

Why it matters

This ProductUpdate is relevant to the technology intelligence record because it involves GitHub, Cursor. The source article should remain the factual reference for follow-up coverage.

Key facts
  • labwc / labwc Public Notifications You must be signed in to change notification settings Fork 268 Star 2.8k Conversation grigio commented Oct 2, 2026 Copy link Copy Markdown Description Real transparency blur in terminal like alacritty, it implements Wayland ext-background-effect-v1 #3391 labwc-blur.mp4 How has it been tested?
  • alacritty with blur Checklist The contribution does not contain any AI-generated content The contribution is consistent with our philosophy g added 3 commits October 3, 2026 01:52 Implement ext-background-effect-v1 3beefc5 Add support for the ext-background-effect-v1 protocol (wayland-protocols staging), discussed in labwc#3391 .
  • The protocol implementation is based on the upstream wlroots code (merged for 0.21 in wlroots!5304), ported into labwc since labwc links against wlroots-0.20 which does not provide it: - advertise ext_background_effect_manager_v1 with the blur capability - track the per-surface pending/current blur region, applied on wl_surface.commit (double-buffered state via wlr_surface_synced) - enforce background_effect_exists and surface_destroyed errors - allow the global for security-context clients Only the protocol state is tracked so far: wlroots offers no hook to blur the region behind a surface while rendering the scene graph, so actually blurring (e.g.
  • Keep SSD border above the ext-background-effect blur nodes 0dcf8e4 SceneFX builds the render clip of a blur node with round_up and expands regions by one pixel when the output scale is fractional, so a blur node paints ~1-2 buffer pixels outside of its own box.
  • The blur nodes were created as the bottom-most children of view->content_tree, which renders above ssd->tree, so that spill landed on the SSD border sitting flush against the surface: at scale 1.25 the side and bottom borders were overwritten while the top border, separated by the titlebar, survived.
  • Parent the blur nodes to a new per-view blur_tree kept as the bottom-most child of view->scene_tree, i.e.
Entities in this story

Companies

GitHub→

Products

Cursor→
Related events