Bug 106564 - Notebookbar large drop down arrow horizontal or vertical
Summary: Notebookbar large drop down arrow horizontal or vertical
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
(earliest affected)
Hardware: All All
: medium enhancement
Assignee: Not Assigned
Depends on:
Blocks: Notebookbar
  Show dependency treegraph
Reported: 2017-03-16 07:58 UTC by andreas_k
Modified: 2018-10-24 10:58 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description andreas_k 2017-03-16 07:58:42 UTC

At the past 32 px action icon the drop down arrow is vertical (bottom) to fit with the 24px icons (two rows) it is needed horizontal (right to the label)

Please add this option to the widget
Comment 1 Yousuf Philips (jay) (retired) 2017-04-15 19:28:18 UTC
Yes this feature should be on by default so the down arrow is being appended to the label rather than below the label in order to reduce the amount of vertical space the notebookbar takes up.
Comment 2 Yousuf Philips (jay) (retired) 2017-04-18 19:35:05 UTC
Presently the down arrow is its own separate button in the group button and the label is part of the main button, so in order for the down arrow to appear next to the label, the label will likely need to be part of the down arrow button.

This is how it is in MSO - http://peltiertech.com/wp-content/img200804/Ribbon_CopyPicture.png
Comment 3 andreas_k 2017-04-18 19:45:15 UTC
and how it work on the drop down buttons where the label is left to the icon? than the drop down button is also left to it.

From the UI I think the left to the label drop down arrow has the benefit that
- everything is more align to each other (one button with and without drop down would be on the same height)
- you can save vertical space

so if it's possible to change the implementation I'm for a change.
Comment 4 andreas_k 2018-10-23 19:23:09 UTC
szimon change it to the right work well
Comment 5 Xisco Faulí 2018-10-24 10:58:22 UTC
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.