Repository navigation
Refine install actions and adapt app detail sizing - #16
Merged
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.
Changes
Install and Open now use the primary button style in both cards and app details. Newly installed apps stay in Discover with an Open button until opened, explicitly refreshed, or switched to another simulator. Cancel stays gray and never becomes the default Return action.
Opening an app launches it on the selected device and brings Simulator or Device Hub forward. After both steps succeed, the details close and the app leaves Discover. A launch or presentation failure keeps the app available for retry.
The details sheet measures its collapsed content to fit the app information without scrolling when screen space permits. Expanding Build Details enables scrolling within that height. Download totals remain fixed as the received byte count changes.
Validation
Simulator commands and device presentation were intercepted in UI checks. Actual Simulator or Device Hub window activation still needs verification on a machine with an installed simulator runtime.