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

[NPE][Canary][Prod] Scrolling- When scrolling back to the top, the entire TreeView structure in 'Content' section collapses automatically. #16255

Closed
sakshi173 opened this issue Apr 12, 2024 · 3 comments · Fixed by #16303
Assignees
Labels
difficulty/medium 🤔 Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI kind/regression Something was working, now it isn't project/items 🧾 Categorizes an issue or PR as relevant to items (ItemsControl, ItemsRepeater, ...)

Comments

@sakshi173
Copy link

sakshi173 commented Apr 12, 2024

Current behavior

System.Drawing.Common.8.0.4._.NuGet.Package.Explorer.-.Google.Chrome.2024-04-12.09-42-51.mp4
Uno.Templates.5.1.25._.NuGet.Package.Explorer.-.Google.Chrome.2024-04-12.09-45-27.mp4

Expected behavior

The tree structure should not collapse.

How to reproduce it (as minimally and precisely as possible)

  1. Open NPE https://purple-pond-0688d230f.azurestaticapps.net/ or https://nuget.info/
  2. Click on 'Open' button and go for any .Net file(the file for which the tree view structure depth is more) like for Uno. Templates
  3. Go to 'Content' section.
  4. Click on multiple folders to open.
  5. Notice that when scrolling back to the top, the entire Tree View structure in 'Content' section collapses automatically.

Workaround

No response

Works on UWP/WinUI

None

Environment

No response

NuGet package version(s)

No response

Affected platforms

WebAssembly

IDE

No response

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

@sakshi173 sakshi173 added kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. labels Apr 12, 2024
@jeromelaban jeromelaban added kind/regression Something was working, now it isn't and removed kind/bug Something isn't working labels Apr 12, 2024
@jeromelaban
Copy link
Member

@Youssef1313 could you take a look?

@Youssef1313
Copy link
Member

Youssef1313 commented Apr 15, 2024

@jeromelaban Debugging on Skia as it's better debugging experience there, it looks like parts of the UI are created on a background thread, causing DispatcherQueue to be null (see here and here). This then causes null ref exceptions down the road. But even after avoiding this, the problem still remains. Continuing investigation.

@ramezgerges
Copy link
Contributor

ramezgerges commented Apr 15, 2024

Fixing in #16303, Submitted to WinUI in microsoft/microsoft-ui-xaml#9549

@MartinZikmund MartinZikmund added difficulty/medium 🤔 Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI project/items 🧾 Categorizes an issue or PR as relevant to items (ItemsControl, ItemsRepeater, ...) and removed triage/untriaged Indicates an issue requires triaging or verification difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. labels Apr 18, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
difficulty/medium 🤔 Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI kind/regression Something was working, now it isn't project/items 🧾 Categorizes an issue or PR as relevant to items (ItemsControl, ItemsRepeater, ...)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants