Adding Subitem value to hitTest #9217
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #9216
Description
The issue is that the function is returning the header item value in case of subitem too.
This is because we are not storing the iSubItem value in our local HitTest (which stores information about the hit item)
Fix is to store SubItem details in HitTest (NativeMethods.LVHITTESTINFO_INTERNAL).
On function "ElementProviderFromPoint" call, if there is a SubItem then condition passes, and we return new ListViewSubItem.
Customer Impact
Customer who are using wrong value for subitem in UI Automation will need to update.
This fix is not affecting the UI Automation tree of the ListView.
Regression
N/A
Testing
Sample application is working as expected.
Further testing needs to be done.
Risk
Low
Microsoft Reviewers: Open in CodeFlow