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
NVDA should fall back to EditTextInfo if ITextDocumentTextInfo fails [Outlook 2010/2013 new profiles dialog] #4090
Comments
Comment 1 by Michael Curran <mick@... on 2014-04-24 05:00
Changes:
|
Comment 2 by mdcurran on 2014-04-28 23:21 |
Comment 3 by leonarddr on 2014-05-06 10:29
|
Comment 5 by Michael Curran <mick@... on 2014-06-10 04:33
Changes:
|
Comment 6 by mdcurran on 2014-06-10 04:35 |
Reported by mdcurran on 2014-04-24 04:55
To support RichEdit windows, NVDA will use a TextInfo of ITextDocumentTextInfo if the richEdit api is 1 or higher, and if the window class ends in 'PT'. However, there are some cases, such as in the Outlook 2010 New Profile dialog where probably due to security restrictions, ITextDocument fails. We should in these cases fall back to using EditTextInfo instead. Therefore we must handle this in an implementation of makeTextInfo on the RichEdit NVDAObject.
The text was updated successfully, but these errors were encountered: