Description: Demote/Promote a list item through indentation buttons is only possible in LibreOffice Writer, not in LibreOffice Impress. Tabbed UI doesn't serve an alternative. Steps to Reproduce: 1) First I switched Writer and Impress to tabbed UI. 2) Than I created a numbered list (also works with bulleted list) in Writer and in Impress. 3) I created two items in both lists and try to move the second item to the second indentation level so the second point is a sub-point of the first one. To do this, I searched an menu item in the tabbed UI and found the "Increase Indent" and "Decrease Indent" button in both (Writer and Impress). Actual Results: In LibreOffice Writer, the buttons are moving the indentation of the elements of the list, in LibreOffice Impress it moves the whole list. Expected Results: In Impress and in Writer it is possible to demote and promote the indentation of a list item with the indentation control buttons. Reproducible: Always User Profile Reset: No Additional Info: Possible workaround, only known by advanced users: In Impress, press F11 to open a settings side bar. Select the tab "Properties". If you are in a list, there is a subsection "Lists" with buttons "Demote" and "Promote". This buttons are not available through tabbed UI so you have to use the indentation control buttons if you want to use the tabbed UI or doesn't know the sidebar UI.
Thank you for reporting the problem. for ensure, would you mind to mention the steps to change the UI? which one do you choose? tabbed or tabbed compact?
UI is not important. Reproducible in Impress in master 6.5+. But here's an example of why reproducible doesn't have to be a bug. I assume this is not a bug, due to difference between indent and promote. But instead of closing, I convert it to Documentation to have better explanation why. Help that's now open via F1 Help on those menus is not enough: https://help.libreoffice.org/6.5/en-US/text/shared/02/02140000.html https://help.libreoffice.org/6.5/en-US/text/shared/02/06050000.html Heiko, you wrote in bug 126122: "The indentation works as promotion in case of lists but not for ordinary paragraphs." Please help to formulate Impress specifics, since that's different.
I have used tabbed layout, not tabbed compact.
Timur: The main problem is a usability problem: Only with the tabbed ui, you cannot change the indentation of list items in LibreOffice Impress - you have to use other UIs (like the side bar with F11). Also it is very strange for a user if one button does something in one situation and does another think in a slightly different, but very similar situation. If this behavior is documented or not doesn't really change the usability issue, because a software should be as much as possible self explaining.
Andreas, as this affects the tabbed Notebookbar I thought you might be interested.
Dear kdedk, 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 MassPing-UntouchedBug
Reproduced in LO 7.6: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 8635c9aa8c6f1078a9e220076d5a08daf30077e8 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded In Writer, "increase/decrease indent" have the same effect on list items as "demote/promote outline level" respectively. In Impress, "increase/decrease indent" change the indent of the whole list (and "demote/promote outline level" behaves the same as in Writer). I agree it should be more consistent.
The command/button is probably "Increase indent", which is a different function than "Demote outline level" (that could be found on the right sidebar; it opens as well with the Tabbed UI by clicking the tiny button in the middle). Writer is a complex text editing tool not working with just text boxes like Impress does. And in fact it is not possible to have lists in text boxes. If you copy the text box containing a list from Impress into Writer the drawing object will loose all bullets or numbers. Point is that the PS in Draw/Impress is less powerful and does not support various attributes, see bug 40871 and bug 111921. And asides from consistency it makes sense to indent the whole list in Impress since you typically have only a few items that are not organized hierarchically. But access to demote/promote via the tabbed interface is needed in any case. (In reply to Timur from comment #2) > "The indentation works as promotion in case of lists but not for ordinary > paragraphs." > Please help to formulate Impress specifics, since that's different. "By indentation you either add spacing at the paragraph beginning or increase the outline level (aka ->Demote like 1. => 1.1.) if the paragraph has a list property assigned. However, the function always indents the whole list in Impress and you have to press demote/promote to change the list level." (This needs more text, examples, and writing expertise *g*)
*** Bug 149307 has been marked as a duplicate of this bug. ***
(In reply to Heiko Tietze from comment #8) > The command/button is probably "Increase indent", which is a different > function than "Demote outline level" (that could be found on the right > sidebar; it opens as well with the Tabbed UI by clicking the tiny button in > the middle). So, indeed, promotion/demotion and indent control are two different things. However, in Writer, we are used to promote/demote via the increase/decrease indent buttons. Perhaps _that_ is the problem in terms of UX. When working with hierarchical lists, one is more likely to want to promote/demote, which also affects horizontal placement - but when working with non-list paragraphs, that's not the case. But this is an Impress bug, not a Writer bug, so let me focus on what Impress users should have. > Writer is a complex text editing tool not working with just text boxes like > Impress does. And in fact it is not possible to have lists in text boxes. If > you copy the text box containing a list from Impress into Writer the drawing > object will loose all bullets or numbers. Ok, but Impress w.r.t. text boxes is also "complex" like Writer is, in the sense of having hierarchical lists in textboxes. So why would the considerations which apply to Writer, w.r.t. Inc/Dec Indent vs Promote/Demote, not apply also to Impress? > Point is that the PS in Draw/Impress is less powerful and does not support > various attributes, see bug 40871 and bug 111921. Maybe, but you _can_ increase/decrease the indent of a single paragraph in Impress; and you _can_ promote/demote in a textbox. So, why not offer the same UI in this context as in Writer? i.e. have a pair of buttons which do Inc/Dec in non-list paragraphs, and promote/demote in list paragraphs? > And asides from consistency it makes sense to indent the whole list in > Impress Oh no it doesn't... it's very surprising to users that this is what happens. Because the situation is the same as in writer: Different paragraphs which may be indented independently, and only one is selected/has the cursor. > since you typically have only a few items that are not organized > hierarchically. But access to demote/promote via the tabbed interface is > needed in any case. This is an interesting point: You're raising the question of _why_ a user wants to indent a paragraph that's not bulleted or numbered. To be honest, one of the typical use-cases may be an invalid one: Wanting to achieve the effect of continuing a bulleted/numbered item by a no-bullet/number item with the same indentation. That is achievable by press Backspace at the start of the paragraph, but users are often unaware of this and indent a non-list paragraph instead. Be that as it may!... you could ask the same question about a Writer document. Why would the user want to change the indentation of a non-list paragraph, at all? The answers for Writer are mostly relevant also for Impress. This feature exists, and is justified. Pardon the preaching, but - you need to accept this fact... Bottom line: We should have the same behavior of this button pair as in Writer.
Unless there is a strong reason, inconsistency is bad. Having same actions doing same things in both apps produces much less surprise, makes learning easier. The underlying markup (ODF) allows the same features in text boxes as in Writer's text body, so the limitation is only in implementation. There is a wish to merge the two layout implementations (EditEngine used in text boxes / Impress / Calc, and Writer's layout, so that the same feature set is available universally). So - I haven't seen a compelling reason not to implement this request yet.