Fix chat realtime status and mobile nav#7
Merged
steipete merged 2 commits intoopenclaw:mainfrom May 9, 2026
Merged
Conversation
f7ee478 to
1463d1b
Compare
This was referenced May 9, 2026
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
ChatApp.aria-expanded, and inert main/thread content while open.Why
After the rebase, the sidebar could remain on
ready/Reconnecting…even with an established websocket because legacy$:reactivity tracked the socket object, not state hidden behind the connection getter. The mobile nav also slid over the timeline without a clean modal boundary on small screens.Validation
pnpm fmt:checkpnpm typecheckpnpm lintgo test ./...pnpm test:e2epnpm exec playwright test --grep "mobile navigation"http://localhost:8080/appon desktop, 390px, and 320px viewports