[dev] [dwm] floating rule does not sanitize window geometry from previous WM

[Ricardson]

Hi,

I run dwm with Firefox assigned to tag 1 as floating. I was previously using 1wm, a minimal WM that blindly moves every window to 0,0 on ConfigureRequest with no EWMH awareness. This leaves Firefox with corrupted geometry in its session state.

When switching to dwm with isfloating = 1, dwm inherits that bad geometry as-is Firefox covers the entire screen including the bar, making tags and slstatus invisible.
The interesting part: temporarily switching the rule to isfloating = 0, recompiling, and restarting dwm corrects the geometry because tiling mode recalculates window placement itself. Switching back to isfloating = 1 and recompiling again then works correctly.

This suggests dwm floating mode accepts incoming window geometry without validation, while tiling mode is more resilient because it ignores client-requested geometry entirely. It may be worth dwm clamping floating window geometry against monitor bounds on map, at least to prevent windows from covering the bar.

----
Kind regards,
Ricardson (r1w1s1)