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

replace value property on NVDAObjects with a valueInfo propertyf #233

Closed
nvaccessAuto opened this Issue Jan 1, 2010 · 2 comments

Comments

Projects
None yet
2 participants
@nvaccessAuto
Copy link

nvaccessAuto commented Jan 1, 2010

Reported by mdcurranf on 2008-11-24 05:59
NVDAObjects currently have a 'value' property, which usually is used to communicate the value of a slider or progress bar, or perhaps a text field with no caret etc. However accessibility APIs such as Java Access Bridge, IAccessible2 and UI Automation can provide more info for the value, such as its minimum and maximum values (if its numeric).
Instead, NVDAObjects should have a valueInfo property, which is a dictionary containing values of:
current, min, max.
If min and max are provided, then current, min and max all need to be numeric. However if current exists by itself, then it can be an arbitrary string.
If an API supports both string values and numeric values, the string value should probably be used in preference.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

nvaccessAuto commented Jan 1, 2010

Comment 1 by jteh on 2009-06-23 06:13
Changes:
Milestone changed from 0.6 to None

@nvaccessAuto

This comment has been minimized.

Copy link
Author

nvaccessAuto commented Jan 21, 2010

Comment 2 by mdcurran on 2010-01-21 05:43
A rather old ticket, which is sort of not needed anymore. UIA has been implemented, and we don't really seem to need this anymore.
Changes:
Changed title from "replace value property on NVDAObjects with a valueInfo property" to "replace value property on NVDAObjects with a valueInfo propertyf"
Added labels: wontfix
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.