Bug 102046 - Split and group buttons not exposed correctly on Linux
Summary: Split and group buttons not exposed correctly on Linux
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected)
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
Keywords: accessibility
Depends on:
Blocks: a11y-Linux
  Show dependency treegraph
Reported: 2016-09-10 14:58 UTC by Yousuf Philips (jay) (retired)
Modified: 2023-07-17 09:24 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

LO vs Gedit toolbars in Accerciser (63.22 KB, image/png)
2016-09-14 19:06 UTC, Yousuf Philips (jay) (retired)

Note You need to log in before you can comment on or make changes to this bug.
Description Yousuf Philips (jay) (retired) 2016-09-10 14:58:22 UTC
We have split and group buttons (buttons with menus) in the toolbar, sidebar, and start center, but they are exposed on Linux as only a push button, when they should be exposed as a menu button, so that screen readers can distinguish between the two types.

Other apps do this by having a push button and a toggle button as two separate controls.
Comment 1 Yousuf Philips (jay) (retired) 2016-09-14 19:06:35 UTC
Created attachment 127335 [details]
LO vs Gedit toolbars in Accerciser
Comment 2 QA Administrators 2017-11-17 09:10:15 UTC Comment hidden (obsolete)
Comment 3 Alex ARNAUD 2017-12-01 13:38:33 UTC
Dear all,

I confirm the issue on LibreOfficeDev 6.1 from 2017-11-26.

Best regards.
Comment 4 QA Administrators 2018-12-03 03:58:29 UTC Comment hidden (obsolete)
Comment 5 Alex ARNAUD 2019-01-18 14:08:36 UTC
Hello all,

I can reproduce the issue on LibreOfficeDev 6.3 (VCL GTK3) from 2019-01-16 on Debian 9 "Stretch" (GNU/Linux).

Best regards,
Comment 6 QA Administrators 2021-01-18 04:07:30 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2023-01-19 03:24:46 UTC
Dear Yousuf Philips (jay) (retired),

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

Comment 8 Michael Weghorn 2023-07-17 09:24:41 UTC
Is this still an issue in current LO versions?
At a quick glance, this sounds like tdf#115847, which seems to be no problem anymore according to the last comments in that ticket.