You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the ListView in a Xamarin.Forms or MAUI application on Windows, the automation framework fails to detect the ListView control when the GroupShortNameBinding property is set. This issue appears when grouping is enabled in the ListView, and the GroupShortNameBinding is used to bind the short name of each group
Steps to Reproduce
Run the application using the given Sample Link attached below for Issue1975.
If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.
Note: You can give me feedback by 👍 or 👎 this comment.
HarishKumarSF4517
changed the title
[Windows] The ListView cannot be accessed via automation on Windows when the GroupShortNameBinding property is used.
[Testing] [Windows] The ListView cannot be accessed via automation on Windows when the GroupShortNameBinding property is used.
Jan 24, 2025
Description
When using the ListView in a Xamarin.Forms or MAUI application on Windows, the automation framework fails to detect the ListView control when the GroupShortNameBinding property is set. This issue appears when grouping is enabled in the ListView, and the GroupShortNameBinding is used to bind the short name of each group
Steps to Reproduce
Run the application using the given Sample Link attached below for Issue1975.
Sample Link: Issue1975.cs
Test Link: Issue1975.cs
Expected Behavior:
The ListView should remain fully accessible to automation tools, regardless of the use of the GroupShortNameBinding property.
However, when the GroupShortNameBinding property is set, it makes the ListView inaccessible to automation frameworks on Windows.
Link to public reproduction project repository
No response
Version with bug
9.0.30 SR3
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
No response
Affected platforms
Windows
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output
The text was updated successfully, but these errors were encountered: