Expanded items under Quick Access collapse when the window regains focus

Aberta
  • Algo errado?
#9,235 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
52/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
javascript
Domínio
frontend

Direção de pesquisa

Start by tracing the visibilitychange handler in account-panel/dist/panels/AccountPanel/index.js to ensureCorrectSubscriptionNodes in out/app/index.js, then read resetAndRefreshChildren() in explorer-panel. Reproduce the focus change with expanded Quick Access items and check how child view models are rebuilt. Done means expanded descendants remain open after returning to the window, without breaking refreshes after subscription changes.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Storage Explorer Version

1.47.1

Regression From

No response

Architecture

x64

Storage Explorer Build Number

20261106.18

Platform

Windows

OS Version

Windows 11

Bug Description

When I switch away from Storage Explorer and come back, everything I expanded under Quick Access collapses. The Quick Access node stays expanded, but the containers and folders inside it close every time the window regains focus. Attached Blob, Queue, Table and File services seem to lose their expanded state in the same way.

Analysis (from the shipped JS bundles)
  • account-panel/dist/panels/AccountPanel/index.js registers: 
    document.addEventListener("visibilitychange", () => {
  const hidden = document.webkitHidden;
  hidden ? Host.executeFunction("StorageExplorer.TopLevelNodes.ensureCorrectSubscriptionNodes") : vm.refresh();
});
  • In out/app/index.js, StorageExplorer.TopLevelNodes.ensureCorrectSubscriptionNodes unconditionally runs
    QuickAccessManager.instance.refreshQuickAccessNode() and ResourceTree.refreshChildren(...) on all attached service nodes.
  • refreshQuickAccessNode() → ResourceTree.refreshChildren(["Azure.QuickAccess"]) + expand(["Azure.QuickAccess"]).
  • In explorer-panel, resetAndRefreshChildren() disposes the child group view model and builds a new one, carrying over only the parent's own isExpanded() state. Descendant expansion state is lost.

So a visibility change that isn't a user action triggers a full rebuild of Quick Access, which loses the user's expansion state.

Suggested fixes
  • Only run ensureCorrectSubscriptionNodes when subscription/account selection actually changed (or only when the user leaves the Account panel, not on window-level visibility changes); and/or
  • Make resetAndRefreshChildren() preserve and restore the expansion state of descendants (e.g. by node UID) after reloading.
Workaround

Locally removing the refreshQuickAccessNode() call from ensureCorrectSubscriptionNodes in out/app/index.js stops the collapse (tested on 1.47.1). This confirms the call is the cause. With that change, Quick Access no longer auto-refreshes after subscription changes.

Resource Types

Quick Access - Storage Accounts

Authentication Method

Sign in

Connection Type

Sign in (subscription)

Steps to Reproduce
  1. Pin a storage account or container to Quick Access.
  2. Expand the item and some of its children (e.g. Blob Containers → a container).
  3. Switch to another application (or minimize Storage Explorer), then return.
Actual Experience

Quick Access stays expanded, but every item underneath it collapses. Attached Blob/Queue/Table/File service nodes appear to lose their child state in the same way.

Expected Experience

The Quick Access tree keeps its expansion state.

Additional Context

No response

Linguagem predominante
Sem dados de linguagem
Estrelas
458
Forks
92
Merge médio
17h 57min
PRs com merge (30d)
4

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de microsoft/AzureStorageExplorer

Todas as issues de microsoft/AzureStorageExplorer

Issues semelhantes

Mais issues de Web Dev

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.