Bug 510078

Summary:	Custom Tiling bypasses minimum window size restrictions, causing visual breakage
Product:	[Plasma] kwin	Reporter:	Roke Julian Lockhart Beedell <4wy78uwh>
Component:	Custom Tiling	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED INTENTIONAL
Severity:	minor	CC:	akselmo, notmart
Priority:	NOR
Version First Reported In:	6.4.5
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	A Demonstrative Screenshot Of System Settings A 2nd Demonstrative Screenshot Of System Settings A Demonstrative Screenshot Of Spectacle A Demonstrative Screenshot Of Filelight

Description Roke Julian Lockhart Beedell 2025-09-30 00:29:29 UTC

Created attachment 185379 [details]
A Demonstrative Screenshot Of System Settings

# SUMMARY

Custom Tiling bypasses minimum window size restrictions, which causes visual breakage in, at least, first-party applications.

# STEPS TO REPRODUCE

1. Invoke `systemsettings`.

2. Press “Meta” + “T”.

3. Subdivide the windows *until* (or one past when) they begin to overlap.

4. Press “Shift” whilst you drag its window onto that region.

# OBSERVED RESULT

*Most* Windows are resizable to any arbitrary size, which breaks most:

1. System Settings renders its sidebar behind its content.

2. KDAB's Hotspot's homepage text renders over all other content.

Strangely, GTK 4 (at least, LibAdwaita) windows appear unaffected.

# EXPECTED RESULT

If a window defines a minimum size, the window manager shouldn't silently override that merely because the window is tiled. Either (probably ideally), KWin (and/or the Breeze window decorations) should indicate that the window has been resized to below its minimum-defined size, or it should fail to.

# SOFTWARE/OS VERSIONS

> ~~~
> Operating System: Fedora Linux 42
> KDE Plasma Version: 6.4.5
> KDE Frameworks Version: 6.18.0
> Qt Version: 6.9.2
> Kernel Version: 6.16.8-200.fc42.x86_64 (64-bit)
> Graphics Platform: Wayland
> ~~~

# ADDITIONAL INFORMATION

The point of this issue that I don't see discussion about this anywhere, and I rather need to know whether this is something that application developers should expect to handle, or whether it's unintentional, *and* undesirable. [^1]

[^1]: https://github.com/KDAB/hotspot/issues/713#issuecomment-2859022943

Comment 1 Roke Julian Lockhart Beedell 2025-09-30 00:30:12 UTC

Created attachment 185380 [details]
A 2nd Demonstrative Screenshot Of System Settings

Comment 2 Roke Julian Lockhart Beedell 2025-09-30 00:31:02 UTC

Created attachment 185381 [details]
A Demonstrative Screenshot Of Spectacle

Comment 3 Roke Julian Lockhart Beedell 2025-09-30 00:32:59 UTC

Created attachment 185382 [details]
A Demonstrative Screenshot Of Filelight

Comment 4 Akseli Lahtinen 2025-09-30 08:21:33 UTC

Can confirm, however I'm not sure if this is an issue or if it's intentional: You can also break some apps with window rules, which is what these tiles basically are.

Will set this as resolved - intentional for now, unless someone who knows more about this feature can confirm it's an actual bug.

Operating System: Fedora Linux 42
KDE Plasma Version: 6.5.80
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.16.8-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: AMD Radeon RX 6600

Comment 5 Roke Julian Lockhart Beedell 2025-09-30 10:21:50 UTC

(In reply to Akseli Lahtinen from comment #4)

Thanks! That's my impression, and having it codified is of use.  This should force some more adaptive UIs. However, I presume that that also means that when an application breaks because it's too small, you shan't accept a bug about it? Or might you, if it's Kirigami-based (like FileLight is)?

Comment 6 Akseli Lahtinen 2025-09-30 14:18:35 UTC

(In reply to Roke Julian Lockhart Beedell from comment #5)
> (In reply to Akseli Lahtinen from comment #4)
> 
> Thanks! That's my impression, and having it codified is of use.  This should
> force some more adaptive UIs. However, I presume that that also means that
> when an application breaks because it's too small, you shan't accept a bug
> about it? Or might you, if it's Kirigami-based (like FileLight is)?

I'd say it's very application dependent. So feel free to make bugreports, the maintainers will decide how to go on from there.