Bug 70394

Summary: Outline level/movement arrows don't belong in the Formatting toolbar
Product: LibreOffice Reporter: Tin Man <newsletters>
Component: UIAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: trivial CC: cno
Priority: medium    
Version: 4.2.0.0.alpha0+ Master   
Hardware: Other   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:

Description Tin Man 2013-10-12 07:58:43 UTC
In LibreOffice Impress, the Outline level/movement arrows (Promote, Demote, Move Up, and Move Down) are displayed in the Formatting toolbar.
However, they can't be applied to text objects like the rest of the commands in the toolbar. Instead, they can only be applied in Outline view. Therefore, it would make more sense to have these four buttons in the Outline toolbar.
Comment 1 Cor Nouws 2013-10-30 21:01:26 UTC
Hi Mirek,

I understand your logic ;)
Is the Outline Toolbar available by default too?

Cheers,
Cor
Comment 2 Tin Man 2013-10-30 22:14:44 UTC
(In reply to comment #1)
> Hi Mirek,
> 
> I understand your logic ;)
> Is the Outline Toolbar available by default too?

Yes. (Only in outline view, of course.)
Comment 3 Cor Nouws 2013-10-30 23:06:52 UTC
(In reply to comment #2)

> Yes. (Only in outline view, of course.)

I could have known - if only I use my mouse more often ;)
Comment 4 QA Administrators 2014-05-17 00:34:10 UTC
Dear Bug Submitter,

Please read the entire message before proceeding.

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 INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/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
Comment 5 Tin Man 2014-05-17 07:03:38 UTC
(In reply to comment #4)
> Dear Bug Submitter,
> 
> Please read the entire message before proceeding.
> 
> 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 INVALID due to lack of needed information.
> 
> For more information about our NEEDINFO policy please read the wiki located
> here: 
> https://wiki.documentfoundation.org/QA/FDO/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

What is the requested information?
Comment 6 QA Administrators 2014-06-01 20:30:08 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO