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.

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

Environments Launch splitbutton arrow shows empty flyout for compute systems with no alternative launch options #2574

Closed
nieubank opened this issue Apr 10, 2024 · 2 comments
Assignees
Labels
Area-Environments Issue-Bug Something isn't working or needs investigation Priority-3 Resolution-Fix-Available Available in a release

Comments

@nieubank
Copy link
Contributor

Dev Home version

No response

Windows build number

No response

Other software

No response

Steps to reproduce the bug

Install a compute system extension that only supports launch and no other operations.

see



<SplitButton.Flyout>
<customControls:CardFlyout ItemsViewModels="{x:Bind LaunchOperations}"/>
</SplitButton.Flyout>

Expected result

The split button arrow should not appear (or at least be disabled?).

Actual result

The split button arrow can be clicked resulting in an empty flyout.

image

Included System Information

No response

Included Extensions Information

No response

@nieubank nieubank added the Issue-Bug Something isn't working or needs investigation label Apr 10, 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 10, 2024
@nieubank nieubank added Area-Environments and removed Needs-Triage New issue that the core contributors need to triage labels Apr 10, 2024
@huzaifa-d
Copy link
Contributor

@hamza-usmani this is a P3, since this involves using an extension that only supports launch, i.e. - theoretical.

@huzaifa-d
Copy link
Contributor

Fixed in #3365

@huzaifa-d huzaifa-d added the Resolution-Fix-Committed Fix is checked in, but may take 3-4 weeks before it's in a release label Sep 24, 2024
@krschau krschau added Resolution-Fix-Available Available in a release and removed Resolution-Fix-Committed Fix is checked in, but may take 3-4 weeks before it's in a release labels Sep 25, 2024
@krschau krschau added this to the Dev Home v0.16 milestone Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Environments Issue-Bug Something isn't working or needs investigation Priority-3 Resolution-Fix-Available Available in a release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants