Created attachment 114825 [details] Sample document For a somewhat sophisticated design I ended up with a auto-width frame that is to be treated as a character at the footer line. Inside the frame I have one paragraph that has a two-line high initial enabled. When trying to put the frame right-aligned (using the right-aligned TAB), I found out that it won't work. Looking closer I found that there is extra space at the inner right of the frame (that should adjust it's width to fit the content inside with no extra borders). The extra space is significant: In my case it's several centimeters. While creating a text document, I found out that the first line of the paragraph causes the ill behaving.
(In reply to Ulrich Windl from comment #0) > When trying to put the frame right-aligned (using the right-aligned TAB), I > found out that it won't work. How do you do this? Do you mean in the ruler?
(In reply to Beluga from comment #1) > How do you do this? Do you mean in the ruler? The footer has two pre-defined TAB stops: One at the center A centering one), and one at the right (a right-aligning one). So when I put the frame after the center tab, it should be right-aligned. Actually (as seen in the example) that doesn't matter regarding the problem: The frame is much too wide in ANY context. Just add some text in the first line inside the frame in my example and watch what happens to the right "X".
@Ulrich : when I open your document in LO master dev 500 alpha, the text in the frame is left justified, hence the space on the right, surely, that is the default behaviour ? If I change this with Centre, or Right, or Justify buttons, I get correct results according to my choice - for example right justification does just that, the text is justified all the way to the rightside edge of the frame
@Ulrich : if I've not understood what it is you are trying to achieve, please provide step by step instructions
Created attachment 115090 [details] Snapshot of what I see in LO5 master build left justified
Created attachment 115091 [details] Snaspshot right justified
Created attachment 115129 [details] partial screen shot: How sample document looks for me (LO 4.3.6.2) Hopefully answering comments 3 and comment 4.
Created attachment 115130 [details] partial screen shot: What happens if I add more text to first line (LO 4.3.6.2) Hopefully this shows that there's a major defect in the code.
OK, I can confirm this now that I understand what you are doing Confirmed in Version: 5.0.0.0.alpha1+ Build ID: 950055bcb06c8edcd9062c71184f02bf8e0604e6 Locale : fr_
** 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.1.5 or 5.2.1 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-20160920
Created attachment 127797 [details] Screenscast showing the defect in LibreOffice 5.1.3 (openSUSE) I had 5.1.3 here for testing, and the defect is still there: I added characters at the end of the first line. The whole box increases its width even though the second line was still longer (the box should only increase its width when the first line is longer than the second line).
** 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 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 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Ulrich Windl, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Ulrich Windl, 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
It seems the problem is fixed in version 7.2.7: I treid the original sample document, and I created a completely new one. However I discovered another bug: If the initial first letter should be three lines high, but the text is only one line, the initial has normal size. Likewise when there are just two lines of text (the initial in only two lines high then). Only if the text has at least three lines, the size of the initial is correct. Maybe that's a different bug.
(In reply to Ulrich Windl from comment #15) > It seems the problem is fixed in version 7.2.7: I treid the original sample > document, and I created a completely new one. > However I discovered another bug: If the initial first letter should be > three lines high, but the text is only one line, the initial has normal > size. Likewise when there are just two lines of text (the initial in only > two lines high then). Only if the text has at least three lines, the size of > the initial is correct. Maybe that's a different bug. Thanks for testing. You could open a new report for the other issue. I recommend to first test with a master build, though.