-
Notifications
You must be signed in to change notification settings - Fork 701
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TreeViewItem doesn't always handle IsExpanded binding properly #2112
Comments
Ok I just saw that this is a duplicate of #1790 , I didn't find it before because it was closed. When should i expect this to make it to a stable build? |
@arcadiogarcia the latest pre-release build should already have this fix. Can you use that ? The next stable release build is planned by the end of the month. Thanks. |
@ranjeshj I tried updating to version 2.4.0-prerelease.200203002 but I can still repro the issue, here is my example: https://github.com/arcadiogarcia/ListViewBugRepro |
@kaiguo can you take a quick look please ? I expected this to be fixed with your change. |
@arcadiogarcia the original issue finally got a post from the bot saying it should be in release |
I've tested this out now and this appears to work, though when I rebind the collection, I do see that it does 'blink' between showing the root and having it expanded. |
I have the same problem or a little bit different with my app. https://github.com/HLCaptain/Hypr
What I did:
It gets worse with more data down the road. Children nodes' expansion toggles unexpectadly and interrupts workflow. OS Build: 19043.1110 |
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I am trying to expand/collapse values in a TreeView procedurally by binding the IsExpanded property in each TreeViewNode. This initially works, but there seems to be a bug that break this behavior.
Steps to reproduce the bug
Steps to reproduce the behavior:
Expected behavior
The values of IsExpanded should still be honored after reassigning the value of ItemsSource. It seems that expansion only works correctly for the first tree that is assigned, and fails for the subsequent.
Screenshots
Tree after step 3:
Tree after step 5, note that IsExpanded == true but the node is not expanded:
Version Info
Running 18363
NuGet package version:
Can repro with both the inbox controls and Microsoft.UI.Xaml 2.3.200213001
The text was updated successfully, but these errors were encountered: