-
Notifications
You must be signed in to change notification settings - Fork 693
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
ElementName bindings deeper in ItemsRepeater.ItemTemplate don't work #9715
Comments
Upon checking the issue in the latest version (1.5.240607001) I have identified that the Here is the sample code, with issue and also a workaround solution,
Output: As a workaround, On the As we have migrated all the existing ListView controls to ItemsRepeater and ItemsView, this is a showstopper issue for us. Provide the fix ASAP and also your input on proceeding with the above workaround. |
@michael-hawker @AndrewKeepCoding your thoughts on the workaround please. |
Surprised this would have regressed between releases. Related to #2508 which would be having x:Bind properly work in these scenarios to begin with. FYI @evelynwu-msft. |
Related to #2508, In my case, the ViewModel object will be passed to the Xaml UserControl through Constructor or Dependency Property i.e through code-behind. In such cases I cannot assign x:Name for it, hence the x: Bind is not working. |
@Naveen61097 AFAIK, the fix addressed in v1.5 never fixed this issue. Can you share a reproducible project of your case? |
I created a simpler repro to show the problem. ElementName bindings at root work as expected now, but nested inside don't seem to.
|
One potential simpler workaround than the loaded event would be to bind to root of the template and bind again like so (not ideal but should work)
|
Originally posted by @AathifMahir in #560 (comment)
The text was updated successfully, but these errors were encountered: