search

Bismuth-Forge / bismuth

KDE Plasma add-on, that tiles your windows automatically and lets you manage them via keyboard, similarly to i3, Sway or dwm.
https://bismuth-forge.github.io/bismuth/
Other
2.4k stars 91 forks source link

[Bug]: Initial sizing of Firefox is incorrect #224

Open montblanc8 opened 2 years ago

montblanc8 commented 2 years ago

Summary

Whenever I initially launch Firefox, it is not sized correctly. Initially, I can see that Bismuth is tiling the application correctly, but it is resized in the lower 1/3 of the screen. Despite it's apparent size, I can't interact with the window in the expected way. For instance, if I wanted to add a new tab, I have to click in the blank space where the new tab button would be if it the window were maximized.

As a work around, I can correct this by going into a tiled layout, opening another window (e.g. terminal), and closing the new window.

Steps to Reproduce

This occurs whenever I launch Firefox for the first time. If Firefox is already running and I launch a new instance on a different virtual desktop, it tiles as expected.

Expected behavior

Firefox should be tiled according to the current layout.

Screenshots

Screenshot_20211205_165345

Bismuth version

2.2.0 (AUR: kwin-bismuth)

KDE Plasma version

5.23.4

The platform KWin is running on

X11

Additional context

No response

sdban commented 2 years ago

I can confirm, I am having the same issues. But it doesn't happen all the time. Update: Sometimes, this also happens without Bismuth.

I am not sure if this is just a bismuth issue.

gikari commented 2 years ago

Could anyone record the video of the bug and confirm, that it's only happening with Bismuth enabled?

montblanc8 commented 2 years ago

Attached are the requested videos.

https://user-images.githubusercontent.com/93507523/146313396-fcbe602a-a685-4e8f-93c7-ea41dd0720f1.mp4

In this video, Bismuth is enabled. Around the 12 second mark, you can see that the window has apparently been resized but, to edit the text in the URL bar, I have to click in the black space where the URL bar would be if it were maximized. Around the 23 second mark, I open a terminal using a keyboard shortcut. After closing the terminal, Firefox is displayed correctly.

https://user-images.githubusercontent.com/93507523/146310606-8b9c40f8-d068-4427-9ffb-2ab85d562b55.mp4

In this video, Bismuth is disabled (I did this by going to KDE Settings > Window Management > Window Tiling > Unchecking "Enable window tiling"). Since window tiling is disabled, I believe Firefox opens at the size that was used when it was last closed. At the 10 second mark, I use a keyboard shortcut to maximize the window.

EDIT: The following steps work for me in reproducing the issue: disable window tiling, open Firefox and shrink it to some size less than maximum, close all instances of Firefox (make sure the last window closed is not maximized), turn on window tiling again, then finally open Firefox again.

viperML commented 2 years ago

This issue is not limited to Bismuth, but it also happened to me using AwesomeWM.

The setting General > Startup > Open previous windows and tabs, will make Firefox remember the latest postion before it was closed, and will try to have the same geometry.

The thing is, disabling this feature will also disable the reopening of tabs, which I would want to presserve. I remember hacking a patch to firefox so it does not remember the window size and position, but I don't want to recompile it every time...

viperML commented 2 years ago

After research a bit, this seems to be an open issue in Firefox (see bugzilla#686747, bugzilla#1630251)

privacy.resistFingerprinting = true in about:config seems to be a workaround for this problem