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

ZeroDivisionError exception if UI Automation RangeValue pattern specifies maximum of 0 #2417

Closed
nvaccessAuto opened this Issue Jun 8, 2012 · 1 comment

Comments

Projects
None yet
1 participant
@nvaccessAuto

nvaccessAuto commented Jun 8, 2012

Reported by jteh on 2012-06-08 07:50
NVDAObjects.UIA.UIA._get_value can throw a !ZeroDivisionError if the !RangeValue pattern is supported but returns a maximum value of 0. While strange, I guess we should probably handle this possibility, since it has been seen in the wild. Also, this documentation suggests a default value of 0.0 for maximum.

We haven't seen this yet, but I'm also wondering whether we need to handle negative values here. I haven't found any documentation yet which specifies whether this is legal or not.

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Aug 1, 2012

Comment 1 by jteh on 2012-08-01 00:52
Should be fixed in 5da8300. I don't have any apps that produce this situation, but I've tested the calculations and they seem to be correct.
Changes:
State: closed

@nvaccessAuto nvaccessAuto added the bug label Nov 10, 2015

@nvaccessAuto nvaccessAuto added this to the 2012.3 milestone Nov 10, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment