fix: optimize mobile remote control flows - #27
Merged
Conversation
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.
Outcome
Makes Grok UI practical and safer on phones across 360px–430px widths: a compact five-item bottom navigation, accessible overflow drawer, responsive Fleet session cards, reachable remote chat and permission controls, safe-area handling, and robust focus restoration for touch, keyboard, Chromium, and Safari/WebKit.
The remote-control protocol and trust boundaries are unchanged. Commands remain authenticated, idempotent, expiring, reconnect-safe, and host-controlled.
Verification
npm run verify— 87 unit/server tests, type checks, production build, release checkSafety and accessibility
Screenshots
Manual mobile visual QA was completed with sanitized fixture data; no screenshots containing local paths or private data are attached.