Skip to content

NVDA should fall back to EditTextInfo if ITextDocumentTextInfo fails [Outlook 2010/2013 new profiles dialog] #4090

@nvaccessAuto

Description

@nvaccessAuto

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions