Don't use UIATextInfo for DevExpress UIA Elements with Text Pattern without Document range #10918
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Link to issue number:
None
Summary of the issue:
In a broken UIA Text Control by DevExpress, the control exposes a text pattern with a NULL DocumentRange. This causes all sorts of trace backs in NVDA on focus, entering with the navigator object and viewing the log.
It looks like implementing the DocumentRange property is mandatory according to the docs.
Description of how this pull request fixes the issue:
When checking what TextInfo class to use for a DevExpress rich edit control UIA object, also check whether the DocumentRange has a True boolean value.
Testing performed:
Tested that regular UIA text controls still behave as expected, and that the broken controls use NVDAObjectTextInfo instead. Note that's not a viable solution for these controls, but they are broken in many ways and don't expose a cursor using the native Win32 APIs either.
Known issues with pull request:
None
Change log entry: