Closed DavidBitSource closed 1 month ago
Also reproducible with LibreOffice 7.1.1.2 and NVDA 2019.2.1 on Win7x64. LibreOffice 7.1.2.2 wasn't tested.
A very quick test for me seems to show this as working. However this is on a more up-to-date system, Windows11, NVDA 2021.3.5 and LibreOffice 7.3.2.2. Do you get this issue with newer versions of NVDA and LibreOffice. Also does it happen always or only sometimes?
Still reproducible with LibreOffice 7.3.3.2 and NVDA 2019.2.1 (installed) and NVDA 2022.1 Beta 4 (Installer/temporary copy) on Win7x64.
Hit F2 multiple times on the cells A1 to D10. And while doing this, move the cursor in both modes with the arrow keys. Sometimes the braille output is updated as it should and sometimes not.
Furthermore, if you hit Enter and type text or numbers directly after that, the braille output sometimes is also not updated as it should.
This issue occurs less often with NVDA 2022.1 Beta 4 than with NVDA 2019.2.1, but it is still present.
Could you update the issue with clear steps to reproduce.
Please reproduce this issue and provide a log file of the behaviour. Ensure your log level is set to debug in general preferences.
Kind Regards, NV Access Software Developers
I am unable to reproduce this in LibreOffice Calc 24.8.2.1. Windows 11. Every time I edit a cell with f2, the editable content is shown on the display. Closing. Please reopen if this is experienced again with most recent or future stable builds of LibreOffice.
Steps to reproduce:
Actual behavior:
Just the TTS gives you feedback, the braille display doesn't change. This mostly occurs when the TTS announces "text frame".
Expected behavior:
Proper braille ouput in real time, according to the screen and according with the TTS output.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2020.4
Windows version:
7 64 bit
Name and version of other software in use when reproducing the issue:
Libreoffice Calc 7.0.4.2
Other information about your system:
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.
If add-ons are disabled, is your problem still occurring?
yes
Did you try to run the COM registry fixing tool in NVDA menu / tools?