-
-
Notifications
You must be signed in to change notification settings - Fork 783
In ui.browseableMessage, every other line is empty #16995
Copy link
Copy link
Closed
Labels
bug/regressionp3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityrelease/blockingthis issue blocks the milestone releasethis issue blocks the milestone releasetriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Metadata
Metadata
Assignees
Labels
bug/regressionp3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityrelease/blockingthis issue blocks the milestone releasethis issue blocks the milestone releasetriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Steps to reproduce:
Actual behavior:
Every other line is empty when screen layout is off.
Expected behavior:
The content should not contain empty lines between useful lines; screen layout should not have any impact here.
NVDA logs, crash dumps and other attachments:
N/A
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
Version : source-master-c8a847b (2024.4.0.0)
Windows version:
Windows 10
Name and version of other software in use when reproducing the issue:
N/A
Other information about your system:
N/A
Other questions
Does the issue still occur after restarting your computer?
Not tested, probably yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
2024.3rc1 is OK, i.e. no such issue.
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Not tested, probably unrelated.
Notes
This issue is very likely introduced by #16369. Cc @XLTechie.
Thus #12004 has been reintroduced unfortunately.