Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upNVDA should fall back to EditTextInfo if ITextDocumentTextInfo fails [Outlook 2010/2013 new profiles dialog] #4090
Comments
This comment has been minimized.
This comment has been minimized.
|
Comment 1 by Michael Curran <mick@... on 2014-04-24 05:00
Changes:
|
This comment has been minimized.
This comment has been minimized.
|
Comment 2 by mdcurran on 2014-04-28 23:21 |
This comment has been minimized.
This comment has been minimized.
|
Comment 3 by leonarddr on 2014-05-06 10:29
|
This comment has been minimized.
This comment has been minimized.
|
Comment 5 by Michael Curran <mick@... on 2014-06-10 04:33
Changes:
|
This comment has been minimized.
This comment has been minimized.
|
Comment 6 by mdcurran on 2014-06-10 04:35 |
nvaccessAuto commentedApr 24, 2014
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.