NVDA reading characters and lines oddly in multiline edit field if already focused when NVDA starts

[valiant8086]

Steps to reproduce:

1. run NVDA snapshot 2025.1.0.35509
2. sign this page into your github account in Edge browser
3. focus the multiline edit as though you are going to make a comment to this issue. Get out of browse mode into focus mode, so you can arrow around in the edit
4. type something in there like this:

this is a test

is it working like it should?

5. press NVDA+q, then r to restart NVDA. Note you need NVDA to be configured to ask what you want to do.
6. NVDA will restart, and you will immediately go back into focus mode so you can continue editing. It is important that focus is immediately in this multiline edit. If it focuses somewhere else, even on the page, and then you manually focus the edit, you won't likely be able to reproduce.
7. arrow up and down and left and right in the edit area.

Actual behavior:

When I arrow up and down, lines are read in the wrong places. When I arrow left and right, characters are read in the wrong places. The first time you move in either direction, it repeats what you're currently on. It is very difficult to edit because you can't really tell where you are.

Expected behavior:

it should read characters and lines as I arrow around just the way it normally would.

NVDA logs, crash dumps and other attachments:

nvda-old.log

System configuration

NVDA installed/portable/running from source:

portable

NVDA version:

2025.1.0.35509

Windows version:

Windows10ltsc 19044.5371

Name and version of other software in use when reproducing the issue:

Microsoft Edge 133.0.3065.92 (Official build) (64-bit)

Other information about your system:

1. I don't want to instal the snapshot. So if anyone else wants to try to duplicate with an installed one it would be great. I can't reproduce with my installed copy of NVDA 2024.2 on the same computer.
2. I have NVDA set carrot moves review cursor on (NVDA+6), focus moves navigator object on (NVDA+7).
3. I don't really want to create a separate issue for Firefox but I found when I tried it there it just doesn't notice the multiline edit when NVDA restarts, and produces errors when I try to navigate until I press tab then shift+tab. I can do a separate issue for that if needed, I'm just lazy and wonder if one issue will work as they seem pretty related.

Other questions

Does the issue still occur after restarting your computer?

I have no idea

Have you tried any other versions of NVDA? If so, please report their behaviors.

2024.2 is fine when I try this.

If NVDA add-ons are disabled, is your problem still occurring?

yes I disabled every one of my add-ons. Insidentally it would be nifty to have an overall checkbox to disable all, and it still happened when I restarted NVDA.

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

[valiant8086]

I actually feel like this is a duplicate of something, but I can't find it sorry.

[seanbudd]

We can't reproduce this and the log file attached doesn't include interacting with a multi line edit control with arrow keys.
Can you provide a debug log with add-ons disabled?
You can restart NVDA with all add-ons temporarily disabled through the exit dialog. You can also select all add-ons and press disable through the add-on store to do disable/enable in batches.

[valiant8086]

Hopefully this one is more useful. I restarted with add-ons disabled and debug logging. I arrowed about in the edit field, noting it exhibited the problem, then I restarted NVDA and this is the old log that resulted.

nvda-old.log

[seanbudd]

It looks like caret movement isn't registering correctly with NVDA

DEBUG - editableText.EditableText._hasCaretMoved (18:46:13.905) - MainThread (19576):
Caret move detected using event. Elapsed 0.0039649 sec, retries 1
IO - speech.speech.speak (18:46:13.910) - MainThread (19576):
Speaking ['is it still messed up?']
IO - inputCore.InputManager.executeGesture (18:46:14.185) - winInputHook (33908):
Input: kb(laptop):upArrow
DEBUG - editableText.EditableText._hasCaretMoved (18:46:14.200) - MainThread (19576):
Caret move detected using event. Elapsed 0.00499773 sec, retries 2
IO - speech.speech.speak (18:46:14.205) - MainThread (19576):
Speaking ['this is a test']
IO - inputCore.InputManager.executeGesture (18:46:14.523) - winInputHook (33908):
Input: kb(laptop):upArrow
DEBUG - editableText.EditableText._hasCaretMoved (18:46:14.640) - MainThread (19576):
Caret didn't move before timeout. Elapsed: 0.107413 sec
IO - speech.speech.speak (18:46:14.644) - MainThread (19576):
Speaking ['this is a test']
IO - inputCore.InputManager.executeGesture (18:46:14.840) - winInputHook (33908):
Input: kb(laptop):upArrow
DEBUG - editableText.EditableText._hasCaretMoved (18:46:14.958) - MainThread (19576):
Caret didn't move before timeout. Elapsed: 0.111202 sec
IO - speech.speech.speak (18:46:14.966) - MainThread (19576):
Speaking ['this is a test']
IO - inputCore.InputManager.executeGesture (18:46:15.289) - winInputHook (33908):
Input: kb(laptop):downArrow
DEBUG - editableText.EditableText._hasCaretMoved (18:46:15.300) - MainThread (19576):
Caret move detected using event. Elapsed 0.00408149 sec, retries 2
IO - speech.speech.speak (18:46:15.304) - MainThread (19576):
Speaking ['this is a test']