-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[Accessibility] Pressing Up/Down keyboard in drop-down list of property collapses drop-down directly #12434
Comments
@LeafShi1 you were working on a related issue with drop downs. Should we make sure fixing this behavior is included in your fix before we service? |
This problem occurs in the drop-down box that is expanded by the shortcut key after changing the property value, and this problem occurs in all properties. I am investigating this problem. The call stack:
We can backport to 9.0 together after this problem is fixed |
Verified this issue in the latest .NET 10.0 SDK build: 10.0.100-alpha.1.24611.5 + binaries built from the main branch of Winforms repo, the issue has been fixed: When Pressing Up/Down keyboard in drop-down list of property does not collapses the drop-down list. Issue12434-Fixed.mp4 |
…r experience in dropdown type editors in property grid (#12605) Backport of #12508, #12431, #12356 and #12479 to release/9.0 Fixes #12607 NET10 Bugs: #12434, #12421, #12440, #12031 Bug Description There are four issues that occur when using the up/down keys to switch property values in the property page. When navigating to "Auto Size" dropdown using the up/down arrow keys, it is getting auto selected without hitting ENTER After using Tab to switch property values, then using the up/down keys to switch items in the drop-down box expanded by F4 will cause the drop-down box to collapse directly [Accessibility] When using up/down to toggle property value on edit text box, The Accessibility rectangle focuses on the entire property row instead of the original edit text box [Accessibility] Narrator cannot announce items correctly when switching the items by using up/down keyboard arrow that without expand the dropdown list panel Customer Impact PropertyGrid drop down type editor does not support conventional keyboard navigation. Usually, selection is committed when the ENTER key is pressed. However, in this case value is committed on the Down arrow press. Then the drop down list is expanded, the screen reader user might want to navigate through all values in the drop down using the arrows, on each arrow key press the new item should be presented (and announced) in the selection text box, however, the drop down is closed on the first arrow key. According to the accessibility SMEs, this is a major problem - the keyboard users are losing their work by committing a wrong value. Screen reader user don't get correct feedback when navigating through the drop down list.
.NET version
10.0.100-alpha.1.24553.6
Did it work in .NET Framework?
No
Did it work in any of the earlier releases of .NET Core or .NET 5+?
No, all versions have this issue
Issue description
Pressing Up/Down keyboard in drop-down list of property collapses dropdown directly.
![Image](https://private-user-images.githubusercontent.com/26474449/383492088-2d68ad2b-a52a-4348-ac19-ab94a99e1597.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk3Mjg1MDAsIm5iZiI6MTczOTcyODIwMCwicGF0aCI6Ii8yNjQ3NDQ0OS8zODM0OTIwODgtMmQ2OGFkMmItYTUyYS00MzQ4LWFjMTktYWI5NGE5OWUxNTk3LmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE2VDE3NTAwMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTAzZWU4OGQxOTZmNjlmMDk4MGYyYjg2YjIwNjc3NzgzNTQwNzZmNzY4NmE0YTA1ZjFlNDIyNDMyMWJjN2RhYzcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.uWqxyd8JLYD00Ca-8mw1pnOQlt5oUai3d5bVfcx2k28)
Expand Result: Drop-down list keeps expanding state when pressing Up/Down keyboard, then pressing Enter can collapse it
Steps to reproduce
Repro steps:
The text was updated successfully, but these errors were encountered: