NVDAObjects/UIA: treat looping selectors as combo boxes without value pattern #9113
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.
Hi,
Finally resolving it after three years:
Link to issue number:
Fixes #5231
Summary of the issue:
Looping selectors do not expose value pattern, causing NVDA to not announce currently selected item. This is prominent in Alarms and Clock app and other apps where time picker is involved.
Description of how this pull request fixes the issue:
Looping selectors without value pattern is coerced into NVDAObjects.UIA.ComboBoxWithouValuePattern.
Testing performed:
Tested with Alarms and Clock, Settings and other apps employing time pickers on various Windows 10 releases (builds 17134, 17763, 18305)
Known issues with pull request:
None
Change log entry:
Bug fixes: I advise copying the what's new entry for ComboBoxWithoutValuePattern fix (#6337), adopting the wording to say that the fix now applies to certain time pickers in Windows 10 apps.
Thanks.