bug: no announcements in cell selection mode in libreoffice

[ilyapashuk]

Steps to reproduce:

1. run libreoffice calc
2. open standard filter dialog to set up a filters
3. enable a feature to copy filterd data to the new range
4. when range text field will be in focus, press f2 to switch into the cell selection mode
5. focus will return to the table to make user able to select the range

Actual behavior:

when I use arrow keys to move in the table in cell selection mode, there is no any announcements about cursor position and selection.

Expected behavior:

nvda should announce table movements and selection changes as usual

NVDA logs, crash dumps and other attachments:

will be posted soon

System configuration

NVDA installed/portable/running from source:

installed nvda

NVDA version:

nvda 2022.2

Windows version:

windows 10 enterprice ltsc 1809

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

libreoffice 7.3

cell selection mode in libreoffice is described hear: https://help.libreoffice.org/latest/ro/text/scalc/guide/keyboard.html

[ilyapashuk]

speechlog.txt

hear is speech log:

[seanbudd]

Is this still an issue in 2022.3beta1? #13233 may have fixed this issue

[ilyapashuk]

issue still presents in 2022.3 beta 1.

but when I tried to reproduce the issue, I noticed the following in the nvda's log:

nv1.log

the same error appears in the my 2022.2

[Adriani90]

@ilyapashuk did you disable all addons in NVDA before reproducing this issue?

In general Libreoffice seem not to expose correctly what is selected, or at least I don't understand how it is exposed via the Accessibility API. A similar issue occurs when you open Writer, write "hello" in the first line, press enter, and write "how are you" in the second line. Then go to first line, press shift + down arrow or shift + up arrow; NVDA does not announce anything. Press ctrl+shift+down and up arrow, NVDA reports the line selected for paragraphs. However, if a paragrapph has two lines, NVDA reports only the first one when pressing ctrl+shift+down arrow to select the whole paragraph. Press multiple times shift+down arrow, NVDA will report that the second line is selected and the first line is not selected which is wrong. Both lines are selected. Same occurs for ctrl+shift+down and up arrow.

cc: @michaelweghorn

[Adriani90]

By the way, the error in this log file is not related to this issue, this seems really hard to investigate since it can be due to a behavior in registry, unregistered DLL or what ever.

[michaelweghorn]

@ilyapashuk did you disable all addons in NVDA before reproducing this issue?

I can reproduce that too, without any additional addons. Other than cell selection in "normal" mode, this misbehaves n the described scenario. One (out of probably many) aspects appears to be that the announcement in NVDA queries and wants to use the selection of the table for the announcement, but that is referring to the selection done before choosing cell selection mode for the filter dialog. (?)

In general Libreoffice seem not to expose correctly what is selected, or at least I don't understand how it is exposed via the Accessibility API. A similar issue occurs when you open Writer, write "hello" in the first line, press enter, and write "how are you" in the second line. Then go to first line, press shift + down arrow or shift + up arrow; NVDA does not announce anything.

I can't reproduce that here with current development versions of LO and NVDA. It speaks the newly selected text.

Press ctrl+shift+down and up arrow, NVDA reports the line selected for paragraphs. However, if a paragrapph has two lines, NVDA reports only the first one when pressing ctrl+shift+down arrow to select the whole paragraph. Press multiple times shift+down arrow, NVDA will report that the second line is selected and the first line is not selected which is wrong. Both lines are selected. Same occurs for ctrl+shift+down and up arrow.

It seems to me that maybe NVDA just announces the newly selected text, and e.g. also just says "how are you, unselected" when unselecting the second line again. What I've seen from time to time is that screen readers do not always reliably announce focused text in Writer, maybe there's some race condition or somesuch in Writer. But I'd generally not mix selection in Writer with selection in Calc (which this issue is about). In particular since there are different methods for handling general selection (e.g. IAccessible::get_accSelection and IEnumVARIANT) vs. the text interfaces.