#Bug: window frame becomes visible when using full screen, transparency and switching virtual desktop

10 messages · Page 1 of 1 (latest)

sleek tangle
#

I use Warp with transparency in Windows 11. When I go fullscreen (F11), move to a different virtual desktop (Win + arrow) and come back, the background window frame becomes visible and persists. Seems like a bug but could be a Windows limitation?

faint carbonBOT
#

Hi @sleek tangle. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

This sounds like a rendering/transparency bug specific to the combination of fullscreen mode, window transparency, and virtual desktop switching on Windows 11.

Based on the available knowledge sources, there is a related known issue: a macOS regression where the title bar would become transparent in fullscreen windows was fixed in the 2025.03.05 release [Changelog]. However, the knowledge sources do not explicitly mention your specific scenario (fullscreen + transparency + virtual desktop switching on Windows 11).

There are also known limitations around window transparency on Windows more generally — for example, transparency may not work correctly with certain GPU drivers or rendering backends [Size, Opacity, & Blurring].

Recommended steps:

  1. Check your graphics backend — Try switching to Vulkan or OpenGL under Settings > Features > System > Preferred graphics backend, as this can resolve some transparency-related rendering issues on Windows. [Size, Opacity, & Blurring]

  2. Check your GPU driver — If you have an Nvidia 572.xx or AMD 23.10.x driver or above, there are known issues where Warp fails to render transparency correctly. Setting the Vulkan/OpenGL render method to "Prefer Native" in your GPU control panel may help. [Known Issues]

#
  1. Report the bug — Since this specific combination (fullscreen + virtual desktop switching + transparency) isn't documented as a known issue, it's worth filing a GitHub issue with logs attached. You can gather logs via Command Palette (Ctrl + Shift + P) > "View Warp Logs". [Sending Feedback & Logs]

The knowledge sources don't confirm whether this is a Windows limitation or a Warp-specific bug, so reporting it with logs would be the best way to get a definitive answer from the Warp team.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@sleek tangle Kapa.ai is still learning and improving, please let me know how I did by reacting below.

alpine fog
#

probably a bug @sleek tangle. @faint carbon please provide the instructions for opening a new github bug report, maybe with the new /feedback skill?

faint carbonBOT
#

Let me check the knowledge base for you again. One moment! :books:

#

Here's how to file a bug report for this issue:

Option 1: Use /feedback in Warp (Recommended)

Type /feedback directly in the Warp terminal. What happens next depends on whether AI is enabled for your account: [Using /feedback in Warp]

  • AI enabled — The Agent will classify your report, ask clarifying questions if needed, check for duplicates, and file the issue in warpdotdev/warp for you. Note this consumes credits.
  • AI disabled — Warp opens the GitHub new-issue picker in your browser with your Warp version and OS prefilled.

Option 2: File a GitHub Issue Directly

Go to github.com/warpdotdev/warp/issues/new/choose and open a new bug report. [Contributing to Warp]

What to Include in Your Report

A good bug report should answer: [What to Include]

  • What happened? — Window frame becomes visible after fullscreen + virtual desktop switch + transparency on Windows 11.
  • What did you expect? — Transparency should persist correctly after switching virtual desktops.
  • Steps to reproduce — Enable transparency → go fullscreen (F11) → switch virtual desktop (Win + arrow) → return.
  • Warp version — Find it under Settings > Account.
  • Logs — Gather them by running the following on Windows, then attach the zip: [Gathering Warp Logs]
#
Compress-Archive -Path "$env:LOCALAPPDATA\warp\Warp\data\logs\*" -DestinationPath "$env:USERPROFILE\Desktop\warp-logs.zip"
  • Environment details — Windows 11, GPU driver version, and your current graphics backend setting (Settings > Features > System > Preferred graphics backend).

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@alpine fog Kapa.ai is still learning and improving, please let me know how I did by reacting below.