fix: polish live surface loading states#31
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
1 participant
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
Fixes two UI states that looked stalled or visually inconsistent in the Ask UI web workbench: the Agent working placeholder now animates, and the live device screen keeps the phone hardware frame after video starts rendering.
What Changed
DeviceShellrendered inside a phone hardware frame instead of switching to a bare screen rectangle.apps/bridge/web.Why
The fixed Agent working row looked like a frozen placeholder. The live device surface also lost its phone shell when the real screen appeared, creating a jarring transition from loading to rendering.
Test Plan
npm test -- src/components/live-app-surface/DeviceShellStructure.test.tsnpm run build:bridgedart run tool/validate_release_layout.dart