Is your feature request related to a problem? Please describe.

List of problems that the new Approach (always using NVDAObjectTextInfo to read objects that isn't navigable in object review and when reporting the line under the caret) causes.

• Unable to navigate display model text while the navigator object is located on ither a WindowRoot, or a ContentGenericClient.
• Unable to read the help window in sasm.
• Unable to read the visual text on the notepad status bar in windows 11.
• When pressing NVDA+l while focused on the help window in sasm, the name of the object is reported. When pressing up or down arrow, the first line of text is reported. NVDA+l should report this instead, as it used to do.

Describe the solution you'd like

use the navigator objects text info in object review and when reporting the line under the caret, as it is done in earlier versions.

Describe alternatives you've considered

Additional context

nvda_beta.log