Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
6.7.3, 6.8.0
-
None
-
Windows 10, NVDA2024.3.1, MSVC2019, QT6.7.3
Windows 10, NVDA2024.3.1, MinGW, QT6.8.0
Description
PlaintextEdit and TextEdit both exhibit the same issue as follows:
1. If I have the following text in the window:
(note line1-line 2 has 2 blank lines, and line2-line 3 has one blank line).
Line 1 Line 2 Line 3
2. When using a braille display and NVDA (2024.3.1), I move the cursor to "Line 1", and
Braille display shows "Line 1" andputs the cursor at the start of it
Speech says "Line1" - in fact, using the Speech Viewer in NVDA, the Speech is actually "Line1\n\n" - but the linefeeds are not spoken.
3. I then move the cursor down to the first blank line under Line 1, and
Braille display shows "Line 1" and leaves the cursor at the end of it
Speech says "Line1" - in fact, using the Speech Viewer in NVDA, the Speech is actually "Line1\n\n" - but the linefeeds are not spoken.
I would expect the speech to say "blank line" or something similar in this case
4. Moving down to the second blank line, and
Braille display is unchaged from '3' above
Speech re-says exactly the same as '3' above
5. Moving down to Line 2, and
Braille display shows "Line 2"
Speech says "Line2", but Speech viewer shows "Line2\n" - i.e. just the one linefeed.
6. If I move the cursor to the '2' in Line 2, and move right, the speech says:
2, linefeeed, L, I, N, E, 3
------
7. If I now put a space on each of the blank lines, and move down through the document, the speech says:
Line1 blank blank Line 2 blank Line3
7. if I navigate back through the document with the left arrow, the braille speech speaks the spaces and the linefeeds.
—
As it is, the VI user is unable to determine which line they are on when there are blank lines in the dialog.
—
I would expect blank lines to cause NVDA say 'blank', and show a blank line on the braille display.
—
To re-create:
Build the attached
Run NVDA
Turn on the NVDA Braille viewer and Speech viewer
Click onto the textedits, and navigate around with the arrow keys
I will also add that I've tried this with Narrator too (just the voice), and on first glance, it seems to work, and navigating down the document Narrator speaks the newlines. But using the up arrow and navigating back through the document, Narrator does speak the contents of the line several lines above the current newline.
This leads me to believe that the cause is something that is common to NVDA and Narrator, which for me is probably Qt.