Bug 118508 - Accessibility events missing when entire row/column unselected in Calc
Summary: Accessibility events missing when entire row/column unselected in Calc
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
Keywords: accessibility
Depends on:
Blocks: a11y-Linux
  Show dependency treegraph
Reported: 2018-07-02 20:20 UTC by Joanmarie Diggs
Modified: 2023-09-15 03:05 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

aforementioned pyatspi accessible-event listener (277 bytes, text/x-python)
2018-07-02 20:20 UTC, Joanmarie Diggs

Note You need to log in before you can comment on or make changes to this bug.
Description Joanmarie Diggs 2018-07-02 20:20:01 UTC
Because Calc doesn't notify Orca when an entire row or column has become unselected, Orca cannot notify the user.

Steps to Reproduce:
1. Launch the attached pyatspi accessible-event listener in a terminal
2. Launch Calc and give focus to the spreadsheet table
3. Press Shift+Space to select a row or Ctrl+Space to select a column
4. Use Shift + Arrows to select a couple more rows/columns
5. Use Shift + Arrow in opposite direction to unselect what became selected in step 4

Actual Results:
Each time step 4 is performed, the event listener prints out an event (good).

Each time step 5 is performed, the event listener does NOT print out an event (bad).

Expected Results:
Each time step 4 or step 5 were performed, the event listener would print out an event.

Reproducible: Always

User Profile Reset: No

Additional Info:
Comment 1 Joanmarie Diggs 2018-07-02 20:20:35 UTC
Created attachment 143273 [details]
aforementioned pyatspi accessible-event listener
Comment 2 Samuel Thibault 2018-07-04 08:15:00 UTC
I can confirm the issue.
Comment 3 Frans-Willem Post 2018-08-03 09:44:59 UTC
I can confirm the issue

Build ID: 1:6.0.3-0ubuntu1
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: nl-NL (en_US.UTF-8); Calc: group
Comment 4 QA Administrators 2021-01-18 04:08:02 UTC Comment hidden (obsolete)
Comment 5 Samuel Thibault 2021-01-19 00:30:52 UTC
This is still a concern with version
Comment 6 QA Administrators 2023-09-15 03:05:37 UTC
Dear Joanmarie Diggs,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team