feat(mobile): add opt-in terminal controls - #185
Draft
Lint111 wants to merge 1 commit into
Draft
Conversation
Unify keyboard-open and keyboard-hidden terminal navigation behind one opt-in setting. Add swipe, simultaneous Up+Down Enter, exposed volume-key mapping, modal suppression, and optional haptic or sound feedback while preserving upstream path-picker actions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add one opt-in mobile terminal control system with responsive surfaces for keyboard-open and keyboard-hidden states.
Controls
navigator.vibrateis availableInteraction Safety
Settings and Migration
truepreferences migrate to enabled.extendedKeyboardBar: falseand device detection alone do not enable the new controls.Volume Keys
Codeman maps browser
keydownevents reported as volume up/down and applies the same simultaneous-direction Enter chord. This is progressive enhancement only: most mobile browsers reserve physical volume keys at the operating-system level and do not expose those events to web pages. The visible controls are the reliable interface.Validation
npx vitest run --config config/vitest.config.ts test/mobile-navigation-pad.test.tsnpx vitest run --config test/mobile/vitest.config.ts test/mobile/navigation-pad.test.tsnpx vitest run --config test/mobile/vitest.config.ts test/mobile/settings.test.tsnpx vitest run --config test/mobile/vitest.config.ts test/mobile/keyboard.test.ts -t "control rows|unified terminal-control|unified controls|accessory bar"npm run check:frontend-syntaxnpm run buildScope
This PR does not change terminal tap classification, draft/IME/paste handling, PTY viewport ownership, or terminal-history streaming. Those are separate review slices.