Created attachment 44258 [details]
Accerciser screenshot: Spin Button exposes ROLE_PUSH_BUTTON to AT-SPI.
A spin button in Libre Office calc spreadsheet doesn't expose ROLE_SPIN_BUTTON to
AT-SPI. It exposes ROLE_PUSH_BUTTON. If it exposes the correct role viz.
ROLE_SPIN_BUTTON, assistive tools like a screen reader can use the information
to improve accessibility of the spreadsheet.
Steps to reproduce:
1. Start Libre Office calc. Create a new spreadsheet. Add a spin button. Turn Design Mode off. Save the spreadsheet.
2. Start Accerciser accessibility explorer.
3. Go to the accessible tree view at top left. As shown in attached screen-shot, select the accessible object corresponding to the spin button just created. The Role column shows 'push button'.
4. In the plug-in view at top right, select Interface Viewer. The first line
shows the role as 'push button'. though the name shown is Spin Button 1.
5. Go to the IPythonConsole at bottom. Command acc.getRole() returns the role
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Today I rechecked my observation with Libre Office dev 3.5.0 beta2 and found
that the bug persists. I suggest that the bug be moved back to NEW status.
Dear bug submitter!
Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.
To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement
Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.
I don't know how I missed the bugmail, but this was never addressed.
Corresponding Apache OpenOffice bug: https://issues.apache.org/ooo/show_bug.cgi?id=117274
** Please read this message in its entirety before responding **
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 on a currently supported version of LibreOffice (4.4.1 or later)
*If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
*If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System
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)
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: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2015-04-01
This happens also in writer, so changing the component. Confirmed that it happens in both gtk2 and gtk3 builds of LO and doesnt happen on windows.