[Feature] Improve Toolkit controls support for Gaze #4649
Replies: 4 comments
-
I'm not sure when we want to do this work yet, but could be a good spot if anyone with a gaze device wants to help us understand any gaps once we get PR #3427 in and testable with our MyGet packages or a NuGet preview. |
Beta Was this translation helpful? Give feedback.
-
There's definitely an issue with ComboBox for base controls, the cursor doesn't go into the Popup/dropdown and the highlight rectangles don't properly highlight the right items. This worked a bit better in the C++ version, but only with highlighting the ComboBox itself, beyond that it had the same other issues once the dropdown was open. See discussion here |
Beta Was this translation helpful? Give feedback.
-
Does the C++ version also have those issues so are those issues then same when using ComboBox? |
Beta Was this translation helpful? Give feedback.
-
@Janisku7 yes, as far as I could tell the original C++ version had the same fundamental issue, though the behavior was a bit different. Ultimately though, once the ComboBox was opened, the user was unable to easily visualize and coherently select an item from it with gaze. |
Beta Was this translation helpful? Give feedback.
-
Describe the problem this feature would solve
Windows exposes interfaces like
IExpandCollapseProvider
to help with automation. Things like ourExpander
control should implement this interface to help with things like Gaze and other input/accessibility tools.Describe the solution
We should evaluate all toolkit components and interfaces and decide which ones would make sense to implement/support. This may also be a matter of ensuring we're using the right base components in controls which already should support some of these interfaces. It may also just be a matter of testing and validating some of these scenarios. There's a bit of 'unknown' here.
Beta Was this translation helpful? Give feedback.
All reactions