Bug 166418 - Atspi.Table.get_accessible_at() returns a different cell for the same coordinates
Summary: Atspi.Table.get_accessible_at() returns a different cell for the same coordin...
Status: NEEDINFO
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
25.2.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: a11y-Linux
  Show dependency treegraph
 
Reported: 2025-05-01 09:40 UTC by Joanmarie Diggs
Modified: 2025-11-25 15:27 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joanmarie Diggs 2025-05-01 09:40:53 UTC
Description:
The fact that Atspi.Table.get_accessible_at() returns a different cell for the same coordinates interferes with some logic in Orca.

Steps to Reproduce:
1. Launch Calc
2. Launch Accerciser
3. Select the accessible object with role table in Accerciser
4. In Accerciser's iPython console, type the following:

table = acc.queryTable()
table.getAccessibleAt(0,0) == table.getAccessibleAt(0,0)

Actual Results:
False

Expected Results:
True


Reproducible: Always


User Profile Reset: No

Additional Info:
Orca makes decisions about what to present based on comparing objects. If object1 and object2 are, for all intents and purposes the same accessible object, an equality check should not fail. When it fails, Orca might double-present / repeat information.

Version: 25.2.3.1 (X86_64)
Build ID: 520(Build:1)
CPU threads: 48; OS: Linux 6.14; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 1 Michael Weghorn 2025-05-01 16:44:55 UTC
Unfortunately, I can't reproduce, neither with LibreOffice 25.2.2 as packaged in Debian testing, nor my current development build. I get this for both the "Sheet Sheet 1" table object selected in Accerciser for a newly created Calc spreadsheet:

    In [19]: table.getAccessibleAt(0,0) == table.getAccessibleAt(0,0)
    Out[19]: True

Do you see the issue with a newly created Calc sheet? Any other ideas what might be a relevant difference in our setups?

Version: 25.2.2.2 (X86_64) / LibreOffice Community
Build ID: 520(Build:2)
CPU threads: 32; OS: Linux 6.12; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Debian package version: 4:25.2.2-1
Calc: threaded

Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 56d64a40c1a257de817406130ca6551d0f3233bf
CPU threads: 32; OS: Linux 6.12; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded
Comment 2 QA Administrators 2025-11-25 15:27:14 UTC
Dear Joanmarie Diggs,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
 
Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-NeedInfo-Ping