Warp improperly renders Window Opacity

Open
#2,772 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
macos, rust

Research direction

Reproduce on macOS by opening Settings → Appearance, changing Window Opacity below 100, then changing content or layout. Start by tracing the window-opacity and rendering behavior described in the issue; done means content updates without recursive afterimages, slow fade-out, or stop-motion artifacts.

Written by the indexing model from the issue text.

Description

area:window-tabs-panes bug ready-to-implement triaged
Discord username (optional)

No response

Describe the bug

Warp recursively renders its own content as if it was a background. All previous renders are combining with some very slow fade-out.

Moreover, this looks like some kind of stop-motion with slow update frequency of renders

To Reproduce
  1. Open Warp
  2. Go to "Settings -> Appearance"
  3. Set "Window Opacity" to any value except 100
  4. Exit Settings
  5. Try any action which changes content or the overall layout
    • Execute commands and watch their input
    • Open various panels and panes
    • Resize the window
    • Move the window around

Captured this behaviour on video (attached)

Expected behaviour

No response

Screenshots

https://user-images.githubusercontent.com/44438314/225049383-82035915-8809-4637-a936-10924df9e1f5.mov

Operating System

MacOS

OS Version

10.14.6

Shell Version

zsh 5.8 (x86_64-apple-darwin18.7.0)

Warp Version

v0.2023.03.07.08.02.stable_01

Additional context

This blocks me from using this convenient transparent appearance

Does this block you from using Warp daily?

No

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

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 warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.