mirror of
https://github.com/NanmiCoder/cc-haha
synced 2026-07-16 13:03:31 +08:00
e0b74cecae
The Windows desktop shell was rendering custom minimize, maximize, and close buttons without the Tauri capabilities those commands require. The app was also starting with decorated windows and then trying to disable decorations at runtime, which is a weaker setup than the platform-specific config Tauri expects for custom chrome. This change grants the missing window permissions, moves Windows and macOS window chrome settings into platform-specific Tauri config files, removes the runtime decoration toggle, and adds a regression test that proves the custom controls invoke the Tauri window API. Constraint: Windows build validation will happen on the remote branch instead of this macOS workspace Rejected: Keep runtime set_decorations(false) on Windows | leaves window chrome behavior dependent on post-start native mutation Rejected: Ship only the capability fix | lower-risk hotfix, but it preserves the fragile cross-platform window config Confidence: medium Scope-risk: narrow Reversibility: clean Directive: Keep custom titlebar behavior in config and capabilities; avoid moving Windows decoration changes back into runtime setup Tested: cd desktop && bun run lint Tested: cd desktop && bun run test Not-tested: Native Windows click/drag behavior on an actual packaged build from this local machine Related: GitHub issue #62