Sway spawns empty container upon entering fullscreen in qutebrowser

[lokesh-krishna]

• Sway Version: 1.6

• Debug Log:
  sway.log

• Configuration File:
  Can reproduce with default config

• Description:

  • Launch qutebrowser (2.2.0) and use an in-tab full screen button to enter fullscreen while in tabbed mode
  • Exit full screen
  • Sway shifts back to tiled mode and there is now an empty container
  • Repeating the process keeps generating empty containers

[vilhalmer]

It appears the parent container of qutebrowser is what actually gets fullscreened, as there is a container border visible in fullscreen.

[rpigott]

Hmm I think this was also reported in #6116.

[rpigott]

@lokesh-krishna Can you test #6207?

[lokesh-krishna]

Um, I dunno how to do that. Would I be building it and then installing it over my present installation?

[rpigott]

The readme has instructions on compiling from source, and to grab the PR you can git fetch origin pull/6207/head:fix && git checkout fix. You can just run the new sway binary from the build directory after ninja -C build/, no need to install it.

Anyway you don't have to I guess, it just expedites things a bit.

[budsterblue]

@rpigott I've been having the same issue with qutebrowser. I applied the PR as a patch to the sway-git AUR package (double checked to make sure it actually applied), and after some testing, it seems like the PR solves this issue for me. It's been incredibly annoying over the past few days, so thanks so much for the fix, and I hope it gets merged soon.