1. Terminal.Gui/ViewBase/Mouse/View.Mouse.cs (Core Change)
- Changed default binding from LeftButtonPressed to LeftButtonReleased (lines 17-19)
- Updated MouseHoldRepeat logic to restore Released binding when disabled (line 268)
- Updated HandleAutoGrabRelease to support cancellation (only invoke commands if released inside viewport)
- Updated command invocation logic to prevent double-invocation
2. docfx/docs/command.md (Documentation)
- Updated Mouse → Command Pipeline table to reflect new default
- Updated View Command Behaviors table (Released column now shows Command.Activate)
- Added comprehensive note (#11) explaining cancellation behavior and how to revert to old behavior
3. Tests/UnitTestsParallelizable/ViewBase/Mouse/DefaultActivationTests.cs (New Tests)
- Created 13 comprehensive tests (all passing ✅)
- Tests cover: default behavior, cancellation, auto-grab, MouseHoldRepeat, backward compatibility
Test Results:
- ✅ 13/13 new DefaultActivationTests pass
- ⚠️ 6 existing MouseTests need updating (they test old Pressed behavior)
- These are expected failures due to the breaking change
Next Steps:
The implementation is functionally complete. To finish:
1. Update the 6 failing tests in MouseTests.cs to expect Released instead of Pressed
2. Run full test suite to identify any other affected tests
3. Manual testing with UICatalog recommended
The new behavior is working correctly - buttons now activate on release (with cancellation support), matching industry
standards!
* Add View command behaviors table to command.md
Documents how each View subclass handles Activate, Accept, and HotKey
commands. The table provides a reference for understanding what user
actions trigger each command/event in specific views.
Includes:
- 27 View subclasses documented
- User actions mapped to commands (Space/Click, Enter/Double-Click, Alt+Key)
- Notes explaining composite views, display-only views, and special cases
https://claude.ai/code/session_01YX1NAzjQFB6Yii4V1Y6GXM
* Add test plan for View command behavior unit tests
Creates a comprehensive plan for adding/improving unit tests to verify
current Activate, Accept, and HotKey command behaviors for all View
subclasses.
Key features:
- Documents 26 Views with specific test cases for each
- Includes test templates with required comments referencing command.md
- Organized by implementation priority (5 phases)
- Each test must reference the View Command Behaviors table in command.md
- Tests serve as behavioral specifications before upcoming changes (#4473)
https://claude.ai/code/session_01YX1NAzjQFB6Yii4V1Y6GXM
---------
Co-authored-by: Claude <noreply@anthropic.com>
