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
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