SUMMARY *** This issue simply revolves around a gap that appears bellow most applications when they're maximized within a wayland session that only has an application menu bar. Apps I've found prone to this issue are firefox, emacs, steam, yuzu emulator, all wine apps, brave, chromium, discord and probably others I have not tested. Apps that are inmune to this issue that I've found are: dolphin, KDE system settings, alacritty, spotify and keepassXC *** STEPS TO REPRODUCE 1. Enter a wayland session 2. Remove the bottom panel and add an application menu bar at the top. 3. Open firefox, or any of the aforementioned apps and maximize them. EXPECTED RESULT A gap appears at the bottom of the screen. SOFTWARE/OS VERSIONS Linux: Arch Linux, linux-zen 6.0.9 KDE Plasma Version: KDE 5.26.3 Note: When I drag the app to the left or right, giving it a half of the screen; there is no gap at the bottom, and I can stretch through the other half of the screen to make it look properly maximized. Thus the issue is only with the maximize functionality, not kwin or the wayland session.
Created attachment 154497 [details] screenshot
Are you by any chance using a scale factor other than 100%, 200%, or 300%?
(In reply to Nate Graham from comment #2) > Are you by any chance using a scale factor other than 100%, 200%, or 300%? Sorry for the late response. No, using 200%
Are you using Firefox in XWayland mode or Native Wayland mode? You can find this out by visiting "about:support" and going to the "Window Protocol" table row. If you're using Firefox in XWayland mode and it goes away when using native Wayland mode, then this is Bug 459373.
(In reply to Nate Graham from comment #4) > Are you using Firefox in XWayland mode or Native Wayland mode? You can find > this out by visiting "about:support" and going to the "Window Protocol" > table row. > > If you're using Firefox in XWayland mode and it goes away when using native > Wayland mode, then this is Bug 459373. I was. The issue was resolved once I started it in native Wayland. Thank you.
Cool, looks like it's Bug 459373. *** This bug has been marked as a duplicate of bug 459373 ***