fix(desktop): disable backdrop-blur on Linux for perf - #3533
Open
JoeJoeflyn wants to merge 1 commit into
Open
Conversation
JoeJoeflyn
force-pushed
the
fix/linux-backdrop-blur-perf
branch
from
July 29, 2026 13:48
35fa4a3 to
cc1c867
Compare
Chessing234
reviewed
Jul 29, 2026
Chessing234
left a comment
Chessing234
left a comment
Contributor
There was a problem hiding this comment.
Reasonable Linux perf trade. WebKitGTK really does software-composite backdrop-filter, and tagging html.platform-linux at boot is a low-risk switch. Two notes:
navigator.platformis deprecated and can be spoofed;navigator.userAgentData?.platform(or Tauri's OS API) would be more durable long-term, but fine for v1.- The
* { backdrop-filter: none !important }hammer is broad — confirm glass panels that relied on blur still have an opaquebg-*behind them so they don't go translucent. The PR description says they do; if you've spot-checked the thread panel + composer on Arch, I'm good.
Linux WebKitGTK has no GPU-accelerated backdrop-filter path. With 16+ backdrop-blur layers visible, each frame re-blurs all backdrops in software, blocking the main thread — causing sluggish UI and slow loading. Tag <html> with platform-linux class and neutralize backdrop-filter on Linux, falling back to the opaque bg-* colors every blur element already carries. Signed-off-by: JoeJoeflyn <thaitainguyen336@gmail.com>
JoeJoeflyn
force-pushed
the
fix/linux-backdrop-blur-perf
branch
from
July 30, 2026 04:43
8ee8782 to
ab6b668
Compare
Author
Chessing234
reviewed
Aug 5, 2026
Chessing234
left a comment
Chessing234
left a comment
Contributor
There was a problem hiding this comment.
rechecked tip — still the right linux trade. most chrome already carries opaque bg-*, and ComposerDockBackdrop is frost-only so killing blur just makes it a no-op there. fine by me.
Author
|
tks, appreciate it |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Linux WebKitGTK has no GPU-accelerated
backdrop-filter. With 16+ backdrop-blur layers visible (header, composer, action bars, thread panel), each frame re-blurs all backdrops in software, blocking the main thread — causing sluggish UI and slow loading. Tag<html>withplatform-linuxat boot and neutralizebackdrop-filteron Linux, falling back to the opaquebg-*colors every blur element already carries.Related issue
Fixes #3328
Testing
Verified on Arch Linux + Hyprland: app was sluggish with 30 messages in #general. After reload with the fix, UI is responsive. macOS/Windows unaffected (no
platform-linuxclass added).