Skip to content
New issue

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

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

Already on GitHub? # to your account

There is also a red border around the 'Destination blob name' field when the 'Destination blob container' field is invalid #8409

Open
v-xianya opened this issue Dec 30, 2024 · 1 comment
Assignees
Labels
⚙️ adls gen2 Related to hierarchical namespaces (ADLS Gen 2) ⚙️ blobs Related to blob storage 🧪 testing Found through regular testing
Milestone

Comments

@v-xianya
Copy link
Member

Storage Explorer Version: 1.37.0 (104)
Build Number: 20241221.4
Branch: rel/1.37.0
Platform/OS: Windows 11/Windows11/Linux Ubuntu 22.04/MacOS Sequoia 15.2(Apple M1 Pro)
Architecture: x64/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.
  3. Change the access tier to 'Archive'.
  4. Right click the archived blob -> Click 'Copy'.
  5. Open another empty blob container -> Click 'Paste'.
  6. The 'Copy and Rehydrate' dialog appears -> Empty the 'Destination blob container' field.
  7. Check there is no red border around the 'Destination blob name' field.

Expected Experience

There is no red border around the 'Destination blob name' field.

Actual Experience

There is a red border around the 'Destination blob name' field.
Image

@v-xianya v-xianya added ⚙️ adls gen2 Related to hierarchical namespaces (ADLS Gen 2) ⚙️ blobs Related to blob storage 🧪 testing Found through regular testing labels Dec 30, 2024
@richardMSFT
Copy link

I took a look into this behavior and it is by design. The reason is that when the container name is invalid, a proper blob connection cannot be created to validate the blob name. Any changes to the blob name field, therefore, cannot be determined to be valid/invalid. As a result, the blob name field has a red border around it.

Another conversation can be made if the red border is not stylistically appropriate here. Maybe "disabling" the input field would make more sense?

@richardMSFT richardMSFT self-assigned this Jan 3, 2025
@craxal craxal added this to the 1.38.0 milestone Jan 6, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
⚙️ adls gen2 Related to hierarchical namespaces (ADLS Gen 2) ⚙️ blobs Related to blob storage 🧪 testing Found through regular testing
Projects
None yet
Development

No branches or pull requests

3 participants