microsoft / microsoft/AzureStorageExplorer
Blob Container already on tab is not refreshed by clicking on it in Explorer tab
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Storage Explorer Version: 1.7.0
Platform/OS: Windows 10
Architecture: i86
Regression From: Not sure.
Bug description
When a blob container is already opened on a tab and then you refresh the containers list on the Explorer sidepanel and click on the container again, the container's content is not refreshed with the new state.
Steps to Reproduce
- Create a blob container
- Create a file in it
- Open the container on a new tab in Storage Explorer
- Delete the file from API
- Refresh the Blob Containers list on the Explorer panel
- Doubleclick on the container on the Explorer panel (this activates the already opened tab)
- The files are still the same
- If you click on Refresh in the Toolbar, the container is finally refreshed and the file is gone.
Expected Experience
When I click on the container item on the Explorer panel, the opened tab should be updated with the new state as clicking is the act of opening something.
Actual Experience
The UI probably just focuses on the already opened tab instead of re-opening it which means refreshing its content.
Additional Context
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Explorer panel's blob-container item activation and the already-open blob-container tab path; reproduce the sequence with a file deleted through the API. Trace what happens when the existing tab is focused and compare it with the toolbar Refresh action. Done means activating the container from Explorer refreshes its contents so deleted files no longer appear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100