fix(web): make chat app icons theme-aware - #2664
Merged
bobleer merged 1 commit intoAug 29, 2026
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.
Summary
Type and Areas
Type: UI/UX regression fix
Areas: web UI, Remote Connect, device overview
Motivation / Impact
Chat-app marks previously used success or accent coloring and were placed inside tinted framed containers. They now remain recognizable monochrome marks while following the active theme, with connection state communicated by the existing status UI.
Verification
Testing level: fully tested with the focused and repository-prescribed automated Web UI checks. A live Telegram, Feishu, or WeChat bot connection was not exercised.
Reviewer Notes
This change is AI-assisted. It targets 1.0.0-explore because these Remote Connect components are not present on main. The change is presentation-only: no remote protocol, connection lifecycle, locale, persisted shape, or platform adapter behavior changes.
Remote scenarios: the local Remote Control UI path was covered by contract and build-time checks. Remote workspace, Peer Device Mode, and Detached Dispatch behavior are unchanged and were not exercised end to end.
Checklist