Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DevHome Hyper-V Create: The layout of the summary page is not intuitive #2598

Closed
KevinLaMS opened this issue Apr 11, 2024 · 1 comment
Closed

DevHome Hyper-V Create: The layout of the summary page is not intuitive #2598

KevinLaMS opened this issue Apr 11, 2024 · 1 comment
Labels
Area-Environments Issue-Bug Something isn't working or needs investigation Priority-2 Resolution-By-Design This is intended to be implemented this way

Comments

@KevinLaMS
Copy link
Contributor

Dev Home version

No response

Windows build number

No response

Other software

No response

Steps to reproduce the bug

When creating the new hyperv image, you start with

  1. Create a name for it
  2. choose an image
  3. info

But when you hit next, the order is completely different. The page feels like it was authored by some one else.

It should be Name of VM you are creating
Image
then details.
It would be nice to have the info button again, to see if chose the right image.

My proposal below actual, though design should evaluate

image

Expected result

it should naturally flow from previous page

Actual result

It does not. :) see image.

Included System Information

No response

Included Extensions Information

No response
@KevinLaMS KevinLaMS added the Issue-Bug Something isn't working or needs investigation label Apr 11, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage New issue that the core contributors need to triage label Apr 11, 2024
@bbonaby bbonaby added Priority-2 Area-Environments and removed Needs-Triage New issue that the core contributors need to triage labels Apr 11, 2024
@kanismohammed
Copy link

This is by design.

@kanismohammed kanismohammed closed this as not planned Won't fix, can't repro, duplicate, stale Apr 16, 2024
@krschau krschau added the Resolution-By-Design This is intended to be implemented this way label Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Environments Issue-Bug Something isn't working or needs investigation Priority-2 Resolution-By-Design This is intended to be implemented this way
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@KevinLaMS @krschau @kanismohammed @bbonaby