Comment 1 by jteh on 2010-10-10 22:57
When you say "isn't read," what happens instead? Can you tab through the dialog and have it read the controls? Or do you mean it freezes completely?

Assuming it doesn't freeze or the like, please ensure you can read the text with object navigation. If you can, the code you want to examine is NVDAObjects.behaviors.Dialog.getDialogText(). Neither Mick or I have access to this software, so we can't help here. I suspect we'll need to special case this dialog

Comment 2 by aleksey_s (in reply to comment 1) on 2010-10-11 04:36
Replying to jteh:

When you say "isn't read," what happens instead? Can you tab through the dialog and have it read the controls? Or do you mean it freezes completely?

NVDA completely looses the tracking of the focus in this window. When i tab/shift+tab it says nothing. Object nav things that there are no objects in that window at all. But NVDA itself doesn't freeze (e.g. I can perform scripts)
Interestingly, that all works OK in 2010.1.

Comment 3 by jteh on 2010-10-11 04:57
I assume you've checked for debug/debugWarning messages in the log? Nothing there?

Comment 4 by aleksey_s on 2011-02-02 19:27
Fix implemented in e17d94c.
Changes:
Milestone changed from None to 2011.1
State: closed