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

The column order of the original tab changes when dragging and dropping one column header from a split tab to the original tab #7907

Closed
v-xianya opened this issue Apr 26, 2024 · 3 comments
Assignees
Labels
🧪 testing Found through regular testing ✅ merged A fix for this issue has been merged
Milestone

Comments

@v-xianya
Copy link
Member

Storage Explorer Version: 1.34.0-dev (98)
Build Number: 20240426.1
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Sonoma 14.4.1(Apple M1 Pro)
Architecture: x64/x64/arm64
How Found: Exploratory testing
Regression From: Not a regression

Steps to Reproduce

  1. Expand one storage account -> Blob Containers.
  2. Create a blob container -> Upload one blob -> Split the blob container tab.
  3. Go to the split tab -> Drag one column header and drop it to the original tab.
  4. Check the column order of the original tab doesn't change.

Expected Experience

The column order of the original tab doesn't change.

Actual Experience

The column order of the original tab changes.

Additional Context

  1. This issue also reproduces for different services between the split view and the original view
  2. Here is the record:
    0425
@v-xianya v-xianya added the 🧪 testing Found through regular testing label Apr 26, 2024
@craxal craxal self-assigned this Apr 26, 2024
@craxal craxal added this to the 1.34.0 milestone Apr 26, 2024
@craxal craxal added the ✅ merged A fix for this issue has been merged label Apr 26, 2024
@v-xianya
Copy link
Member Author

Verified this issue on the main build 20240428.1. Reproduce.

@craxal
Copy link
Contributor

craxal commented May 1, 2024

@v-xianya We now disallow dropping columns outside of the explorer they're from. The merged changes were in a separate package, hence we moved this to "Verifying" and did not yet close the issue. The changes have now been integrated.

@craxal craxal closed this as completed May 1, 2024
@v-xianya
Copy link
Member Author

v-xianya commented May 6, 2024

Verified this issue on the rel build 20240506.3. Fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🧪 testing Found through regular testing ✅ merged A fix for this issue has been merged
Projects
None yet
Development

No branches or pull requests

2 participants