Wayland/Linux: default WebKit safe flags can hurt responsiveness and decoration behavior

Open
#1,192 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
linux, rust, tauri
Domain
desktop, operating-systems

Research direction

Start by locating the Linux runtime path that sets the WebKit safe-mode environment variables and the Linux window state restore path. Review the linked patch for the proposed opt-in behavior and restore handling, then test on a pure Wayland session. Done means the conservative flags are not forced by default and window decorations remain interactive during startup and restore.

Written by the indexing model from the issue text.

Description

Problem\nOn pure Wayland systems, apps packaged with Pake can feel laggy (text input delays, less snappy UI), and window controls (min/max/close) can become non-interactive depending on compositor/session timing.\n\nCurrent Linux runtime path in sets these env vars by default:\n- \n- \n\nThese help blank-screen cases, but on some Wayland setups they trade off too much interactivity/performance.\n\n## Repro notes\n- Launching with:\n \n noticeably improves responsiveness on my host.\n\n## Suggested direction\nMake the conservative Linux WebKit flags opt-in (or dynamically gated), rather than always-on defaults.\n\nOne practical option:\n- Only set those vars when a dedicated env toggle is present (example: )\n\nAlso consider Linux-specific window visibility/state restore behavior for Wayland to avoid non-interactive decorations during startup.\n\n## Patch reference\nI validated a local patch with:\n- Linux WebKit safe mode made opt-in\n- Linux state flags preserving during restore path\n\nPatch in my fork:\nhttps://github.com/mestadler/Pake/commit/cf519dc

Dominant language
Rust
Stars
61.5k
Forks
12.7k
Avg merge
2d 7h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tw93/Pake

All issues in tw93/Pake

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.