Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Bug: UniformGridLayout can leave empty gaps after resizing while scrolled

Aberta
  • Algo errado?
#869 3 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
48/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
csharp
Domínio
frontend

Direção de pesquisa

Comece reproduzindo o problema com um ItemsRepeater usando UniformGridLayout, virtualização, rolagem e uma alteração da largura em tempo de execução. Inspecione o comportamento do layout e da virtualização durante o redimensionamento e, em seguida, verifique se todos os itens visíveis continuam realizados e posicionados sem lacunas e reaparecem sem rolagem adicional.

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

Descrição

Describe the bug

Describe the bug

UniformGridLayout can leave empty gaps in an ItemsRepeater after resizing the available width while the control is scrolled.

Some items disappear from the viewport, leaving blank spaces where the items should be. Simply scrolling a small amount causes the missing items to reappear.

Steps to reproduce

  1. Display a large collection of items using ItemsRepeater with UniformGridLayout.
  2. Ensure virtualization is active (enough items to require scrolling).
  3. Scroll down several rows.
  4. Resize the available width of the ItemsRepeater (for example by moving a GridSplitter that changes the width of its parent container).
  5. Observe that some visible positions become empty.
  6. Scroll slightly up or down.
  7. The missing items reappear.

Expected behavior

After a width change, all visible items should remain correctly realized and positioned.

No empty gaps should appear.

Actual behavior

After resizing while scrolled:

  • Some items disappear from the viewport.
  • Empty spaces remain where those items should be.
  • A small scroll causes the missing items to reappear.

This suggests the layout/virtualization state becomes inconsistent after the width change.

Environment

  • Windows App SDK: (fill in version)
  • WinUI: (fill in version)
  • Windows version: (fill in version)

Additional information

The issue appears only after the control has been scrolled.

Resizing while already at the top of the list is much harder (or impossible) to reproduce.

The problem is consistently reproducible in a grid using UniformGridLayout with virtualization enabled after changing the available width.

Steps to reproduce
## Steps to reproduce

1. Create an `ItemsRepeater` using `UniformGridLayout` with enough items to enable virtualization and scrolling.
2. Place the `ItemsRepeater` in a layout where its available width can change at runtime (for example, by resizing a neighboring panel with a `GridSplitter`).
3. Scroll down several rows so the viewport is no longer at the top of the list.
4. Resize the available width of the `ItemsRepeater`.
5. Observe that some items disappear, leaving empty gaps in the grid.
6. Scroll slightly up or down.
7. Observe that the missing items immediately reappear.

## Reproducibility

Occurs consistently in this scenario after scrolling and resizing the available width of the `ItemsRepeater`.
Expected behavior

Expected behavior

When the available width of an ItemsRepeater using UniformGridLayout changes, the layout should correctly recalculate the positions of all visible items.

No visible items should disappear or leave empty gaps in the grid. The realized items and scroll extent should remain consistent before, during, and after the resize, without requiring any additional user interaction (such as scrolling) to restore the correct layout.

Screenshots

No response

Code Platform
  • UWP
  • WinAppSDK / WinUI 3
  • Web Assembly (WASM)
  • Android
  • iOS
  • MacOS
  • Linux / GTK
Windows Build Number
  • Windows 10 1809 (Build 17763)
  • Windows 10 1903 (Build 18362)
  • Windows 10 1909 (Build 18363)
  • Windows 10 2004 (Build 19041)
  • Windows 10 20H2 (Build 19042)
  • Windows 10 21H1 (Build 19043)
  • Windows 10 21H2 (Build 19044)
  • Windows 10 22H2 (Build 19045)
  • Windows 11 21H2 (Build 22000)
  • Windows 11 22H2 (Build 22621)
  • Windows 11 23H2 (Build 22631)
  • Windows 11 24H2 (Build 26100)
  • Windows 11 25H2 (Build 26200)
  • Windows 11 26H1 (Build 28000)
  • Other (specify)
Other Windows Build number

No response

App minimum and target SDK version
  • Windows 10, version 1809 (Build 17763)
  • Windows 10, version 1903 (Build 18362)
  • Windows 10, version 1909 (Build 18363)
  • Windows 10, version 2004 (Build 19041)
  • Windows 10, version 2104 (Build 20348)
  • Windows 11, version 22H2 (Build 22000)
  • Windows 11, version 24H2 (Build 26100)
  • Windows 11, version 25H2 (Build 26200)
  • Windows 11, version 26H1 (Build 28000)
  • Other (specify)
Other SDK version

No response

Visual Studio Version

2026

Visual Studio Build Number

No response

Device form factor

Desktop

Additional context

No response

Help us help you

Yes, I'd like to be assigned to work on this item.

Linguagem predominante
C#
Estrelas
1.1k
Forks
170
Merge médio
6d 5h
PRs com merge (30d)
1

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

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 CommunityToolkit/Windows

Todas as issues de CommunityToolkit/Windows

Issues semelhantes

Mais issues de C#

Receba novas issues na sua caixa de entrada

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