Is your feature request related to a problem? Please describe.
On Windows, Wails windows still show the system maximize button. When the user clicks it, the window can resize incorrectly (e.g., jumping to the top-left corner and/or behaving unexpectedly). This makes it hard to enforce fixed-size layouts for apps that require a specific window geometry.
Describe the solution you'd like
Add an option in Wails Windows app options to:
- Disable maximization entirely, and/or
- Hide/disable the maximize button (equivalent to “non-maximizable” window behavior on Windows),
- Ensure that the window remains within the configured bounds (especially when
DisableResize and/or fixed MinWidth/MaxWidth and MinHeight/MaxHeight are set).
Describe alternatives you've considered
Workarounds currently possible:
- Using
Frameless: true to remove the title bar/buttons (but then the app must implement custom window dragging/resizing behavior and potentially looks less native).
- “Unmaximize and revert” logic on the frontend/backend after a maximize attempt (feels hacky and introduces flicker/extra complexity).
- Setting min/max equal values and
DisableResize (but the maximize button still triggers inconsistent Windows behavior).
Additional context
No response
Is your feature request related to a problem? Please describe.
On Windows, Wails windows still show the system maximize button. When the user clicks it, the window can resize incorrectly (e.g., jumping to the top-left corner and/or behaving unexpectedly). This makes it hard to enforce fixed-size layouts for apps that require a specific window geometry.
Describe the solution you'd like
Add an option in Wails Windows app options to:
DisableResizeand/or fixedMinWidth/MaxWidthandMinHeight/MaxHeightare set).Describe alternatives you've considered
Workarounds currently possible:
Frameless: trueto remove the title bar/buttons (but then the app must implement custom window dragging/resizing behavior and potentially looks less native).DisableResize(but the maximize button still triggers inconsistent Windows behavior).Additional context
No response