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

Cursor keys don't work as expected in tree view when creating queue #7703

Closed
3 tasks done
marcelvb opened this issue Jan 25, 2024 · 1 comment
Closed
3 tasks done
Assignees
Labels
🪲 bug Issue is not intended behavior ✅ merged A fix for this issue has been merged
Milestone

Comments

@marcelvb
Copy link

Preflight Checklist

Storage Explorer Version

1.32.1

Regression From

No response

Architecture

x64

Storage Explorer Build Number

20231114.10

Platform

All

OS Version

Windows 11

Bug Description

When creating a queue by right clicking Queues node in the Explorer, the cursor keys don't work as expected. When typing a name for a queue, and I made a typo, I press cursor left. This will not move the cursor, but will move the node in the tree, resetting my action.

Steps to Reproduce

  1. Right click Queues node in Explorer view
  2. Click "Create Queue"
  3. Start typing a few letters
  4. Press cursor left

Actual Experience

The selected node changes, undoing creation of the queue.

Expected Experience

I expect the cursor to move left to edit the typed name.

Additional Context

No response

@MRayermannMSFT MRayermannMSFT added the 🪲 bug Issue is not intended behavior label Jan 29, 2024
@MRayermannMSFT MRayermannMSFT self-assigned this Jan 29, 2024
@MRayermannMSFT MRayermannMSFT added this to the 1.33.0 milestone Jan 29, 2024
@MRayermannMSFT MRayermannMSFT added the ✅ merged A fix for this issue has been merged label Jan 30, 2024
@MRayermannMSFT
Copy link
Member

A fix for this will be included in our 1.33 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🪲 bug Issue is not intended behavior ✅ merged A fix for this issue has been merged
Projects
None yet
Development

No branches or pull requests

2 participants