Created attachment 43666 [details] demonstration problem with first line in paragraph When paragraph is in list, numbered or not, it behaves strange. In dialog "Paragraph" in tab "Indents&Spacing" I have set Before text 7.0 cm and First line -4.0cm. First line should protrude on 4 cm. But it does not. All lines trimmed equal. When I save this file and then open, all looks ok. Firs line protrudes. But when I slightly change this parameters, then problem appears anew. When changing indent of firs line by mouse, one can find positions where this bug not appears.
Created attachment 43917 [details] explanaiton problem with paragraphs I have just reproduced this problem on Libreoffice 3.3.1.2 on Mandriva 2010.2 64 bit and windows XP 32.bit. More explanations and screenshots in attachment.
This is not a bug, but a feature. By sliding this handle you apply the same indent to all the selected paragraphs.
Problem not in that intent the same. In text from firs attachment presents remarkable protrude in first paragraph. After moving slider protrude suddenly disapears. Other paragraphs is nonimportant. Where disapears my outdent from firs line of first paragraph?
Created attachment 43955 [details] improved explanation of paragraph problem Sorry for explanation that hard to understand. I have attached better explanation.
Ok, taking it. MOving the slider is doing weird stuffs with the tabstop after the numbering.
problem remains in 3.5.3, though second attachment look different immediately after opening
** 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) https://www.libreoffice.org/download/ *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) http://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: 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
** 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 (5.0.5 or 5.1.2 https://www.libreoffice.org/download/ 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
** 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 (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
With LO 5.2.7 and Version: 6.0.0.0.alpha1+ (x64) still remains. Just after loading of document we see strange behaviour of the first line i paragraph. Then we move slider on 1cm right (just on one cm): And first line jumps to right.
I can still reproduce it in the original document in: Version: 6.1.0.3 Build ID: 6.1.0-2 CPU threads: 12; OS: Linux 4.18; UI render: default; VCL: gtk2; Locale: de-DE (en_US.UTF-8); Calc: group threaded In the second attached document, the first line is aligned with the others from the start. After all it doesn't seem like a bug to me. It's just the way LO handles tab stops when there are non defined. Numbering is right where first line is defined in the paragraph option. The tab stop after the numbering is what is messing things up.
Created attachment 154075 [details] improved explanation COMPARED OO LO First from OO, there was an inconsistent behavior on some change, but not anymore. Already explained that tab is the cause. MSO behaves similarly. Not clear what is *expected* here. I'll agree and close the bug. If you object, please write expected behavior.