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

Investigate/fix ancestor crawl in IAccessibleHandler.processDestroyWinEvent #2695

Closed
nvaccessAuto opened this issue Oct 1, 2012 · 2 comments
Assignees
Milestone

Comments

@nvaccessAuto
Copy link

Reported by jteh on 2012-10-01 03:37
Brian reported intermittent exceptions and lag when closing apps on his system that wasn't there before. This seems to be due to changes introduced in 62c10a3 to processDestroyWinEvent which walk up the parents for objID child ID 0, apparently for IME/TSF candidate lists. We should consider restricting this or catching the exception. Details can be found in this thread.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2012-10-01 03:40
Mick, the branch we were talking about that might be a useful reference is experimental/deadFocus. However, this idea isn't any use if the composition thingy doesn't get focus, since finding focus won't work.

@nvaccessAuto
Copy link
Author

Comment 2 by mdcurran on 2012-10-03 01:19
ea4beff should fix this. This code can't be made generic as candidate items may have the composition string as their parent. So this code has now bbeen made even more specific to MSAA candidate lists.
Changes:
State: closed

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

No branches or pull requests

2 participants