Skip to content
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

NVDAObjects/UIA: treat looping selectors as combo boxes without value pattern #9113

Merged
merged 4 commits into from
Jan 8, 2019

Conversation

josephsl
Copy link
Collaborator

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.

Remove duplicated 'import time'.
When importing Edge, use relative import to make it Python 3 compliant.
…bo boxes without value pattern. Re nvaccess#5231.

Looping selectors are used to select an item from values that wraps around, especially employed in time pickers 9SEttings, Alarms and Clock and others). Becasue they do not expose values, treat them as combo box without value pattern objects. This then allows NVDA to ask UIA to fetch the selected value by querying the selected element.
@josephsl
Copy link
Collaborator Author

Hi,

I asked mick for a review because he is the one who have investigated combo boxes without value pattern before and knows what might be happening. Also, if he doesn't mind, a second look from @jcsteh is appreciated. Thanks.

@michaelDCurran michaelDCurran merged commit 027b7f1 into nvaccess:master Jan 8, 2019
@nvaccessAuto nvaccessAuto added this to the 2019.1 milestone Jan 8, 2019
@josephsl josephsl deleted the i5231loopingSelector branch April 2, 2019 03:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Windows 10: Time picker values are not announced
4 participants