in NVDA and chromium browsers, NVDA sticks paragraphs together when display: block is present in ::before and ::after

[ogomez92]

Steps to reproduce:

1. Open test.html in Google Chrome or Microsoft Edge (Chromium version).
2. NVDA will speak the following content: First paragraph text goes here.Second paragraph text goes here.Third paragraph text goes here.
3. In the html sample file, comment out both display: block in the ::before and ::after css properties with /* display: block; */.
4. NVDA will announce both paragraphs separately and the user can browse with up/down arrow keys.
5. Remove /* and */ from display block in ::before and ::after, then open the same file in any other browser such as firefox.
6. The content is displayed correctly, with browsable paragraphs.

Actual behavior:

First paragraph text goes here.Second paragraph text goes here.Third paragraph text goes here.

Expected behavior:

First paragraph text goes here.
Second paragraph text goes here.
Third paragraph text goes here.

NVDA logs, crash dumps and other attachments:

Input: kb(laptop):upArrow
IO - speech.speech.speak (10:05:59.864) - MainThread (4240):
Speaking ['First paragraph text goes here.Second paragraph text goes here.Third paragraph text goes here.']
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (10:06:00.092) - Thread-8 (3540):
accRole failed: (-2147417842, 'La aplicación llamó a una interfaz que se aplanó para un diferente subproceso.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (10:06:00.608) - Thread-8 (3540):
accRole failed: (-2147417842, 'La aplicación llamó a una interfaz que se aplanó para un diferente subproceso.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (10:06:01.117) - Thread-8 (3540):
accRole failed: (-2147417842, 'La aplicación llamó a una interfaz que se aplanó para un diferente subproceso.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (10:06:02.139) - Thread-8 (3540):
accRole failed: (-2147417842, 'La aplicación llamó a una interfaz que se aplanó para un diferente subproceso.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (10:06:02.652) - Thread-8 (3540):
accRole failed: (-2147417842, 'La aplicación llamó a una interfaz que se aplanó para un diferente subproceso.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (10:06:03.481) - winInputHook (5264):
accRole failed: (-2147417842, 'La aplicación llamó a una interfaz que se aplanó para un diferente subproceso.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (10:06:03.564) - winInputHook (5264):
accRole failed: (-2147417842, 'La aplicación llamó a una interfaz que se aplanó para un diferente subproceso.', (None, None, None, 0, None))

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

[Window Title]
NonVisual Desktop Access (NVDA)
Version: 2024.4.1 (2024.4.1.34550)

Windows version:

11 (24h2)

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

Google Chrome (this has been happening for a few months no, currently running latest versionw)

Other information about your system:

Microsoft Edge latest version that comes with windows 11, also happening.

Other questions

Does the issue still occur after restarting your computer?

Yes

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

2023.*, 2024.1

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

Yes
test.zip
.

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

Yes.

[ogomez92]

I just wanted to add quickly here that I tested the same file with Chrome on macOSX and the paragraphs are being correctly separated, so it is definitely an NVDA specific issue

[ogomez92]

I have also tested on OSX and narrator and I'm not running into this issue so it's definitely something with NVDA.

[SaschaCowley]

Data URI for those who are into that sort of thing:

data:text/html,%3Cstyle%3Ep::before,p::after%7Bcontent:%22%22;display:block;%7D%3C/style%3E%3Cp%3EFirst%3Cp%3ESecond

[aardrian]

Using JAWS 2024.2409.2 with Chrome 131.0.6778.140 I get the following when loading the data URI and navigating with the virtual cursor:

FirstSecond
Page has no links

↓

FirstSecond

When go into devtools and remove the p::before, p::after selector, I experience the following:

First

↓

Second

JAWS and NVDA are behaving the same, so it could also be the same bug with both screen readers. But since it happens with Chrome / Windows, I suspect Chrome.