Created attachment 108798 [details] Writer document illustrating the example in the description In some circumstances, AutoSize on a Frame fails to expand the width sufficiently. Specifically, this happens when a line contains a single word that is longer than all previous lines. Curiously, this does not happen to all of my Frames, but when it happens, it is reliably replicable. Attached is a sample document. TO DUPLICATE 1. Create a new Writer document, size A4. 2. Insert a Frame. Check AutoSize on both Width and Height. 3. In the text area of the Frame, set the text large (e.g. 88 pt) and type "Check it's worthwhile" (or any words where the first line is shorter than the last word). Alternatively, type "Check this is worthwhile" and delete letters from the first word. This can be extended to having more than two lines, e.g. "Check that this wording is always worthwhile to use." WHAT HAPPENS When the a line with a single word is longer than any previous line, the frame width decreases, causing the second word to wrap. This happens in A4 or Letter, and in Portrait or Landscape (with suitable text sizes and word lengths). WHAT SHOULD HAPPEN The frame should keep its width sufficient for the second line, allowing the second word to remain intact. TESTED ON OPERATING SYSTEMS o Ubuntu 14.04 64-bit o Windows 7 TESTED ON LIBREOFFICE VERSIONS 4.3.3.1 4.4.0.0.alpha1
Sorry, I mistyped the "what should happen" sentence. It should read: The frame should keep its width sufficient for the one-word line, allowing that word to remain intact.
Created attachment 109521 [details] PDF printed using 4.4.0.0 alpha2 from Nov 12 I opened your document and printed it to PDF. Does this exhibit the bug? Win 7 64-bit Version: 4.4.0.0.alpha2+ Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827 TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08
Beluga, that is bizarre. I get the problem whereas you don't. What difference could there be between your set-up and mine? Might we have different options set, perhaps? I am currently testing on Version 4.4.0.0.alpha2, Build ID 24f0a5815f581dd9a7f09d30213a379edee6e9ac. I have Version 4.3.4.1 installed. Would 4.4.0.0.alpha2 be sharing the options from 4.3.4.1? How can I test again with all options reset to the defaults (I'm using Ubuntu 14.04)?
Hey, you are right: on Ubuntu, the word "worthwhile" does get cut off from its last "e". Let's set to NEW and see what happens. I would say severity = minor per this chart: https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg Ubuntu 14.10 64-bit Version: 4.4.0.0.alpha2+ Build ID: 5bff4b016c4b44f4123e0e6a4fd4c0c4dc0cfa2d TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2014-11-13_00:14:29
And yet I had this problem on Windows 7. Confusing! Thanks for checking this.
Bug not observed in 3.3 or 3.5 -> likely regression. Ubuntu 14.10 64-bit LibreOffice 3.5.0rc3 Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735 LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
Agh, I posted to the wrong bug! Last keyword/whiteboard changes reverted. I *can* repro this with: Ubuntu 14.10 64-bit LibreOffice 3.5.0rc3 Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735
I confirm that this bug is still present in 4.4.1.2.
** 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
This bug is still present. LibreOffice 5.1.2.2 Ubuntu 14.04 64-bit
** 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
The bug is still present. LibreOffice 5.3.3.2 Linux Ubuntu 16.04 64-bit
** 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
I have retested this, and unfortunately the problem remains. Help > About LibreOffice: Version: 6.0.4.2 Build ID: 1:6.0.4~rc2-0ubuntu0.16.04.1 CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk2; Locale: en-GB (en_GB.UTF-8); Calc: group Linux Ubuntu 16.04 64-bit Thank you
Dear Paddy Landau, 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
Bug is still present. Help > About LibreOffice: Version: 7.0.4.2 Build ID: 573028415b474775687f7355a6d413c41d013a01 CPU threads: 16; OS: Linux 5.8; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded
Bug still present on LibreOffice 7.4.1.2, tested on Ubuntu 22.04 and Windows 10 Home.
I can't replicate the bug on Windows 10, LO 7.4.1.
(In reply to lomacar from comment #18) > I can't replicate the bug on Windows 10, LO 7.4.1. I have uploaded a brief video (15 seconds; link below) showing what happens. I used the ODT attachment from the original report. Watch what happens as I delete and retype the word "Check". The frame resizes incorrectly, causing the word "worthwhile" to be cut over two lines. https://youtu.be/9X5jtSi03qQ What happens when you try the same thing? This was on Windows 10 Home, using the latest version of LibreOffice, freshly downloaded: Version: 7.4.1.2 (x64) / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 6; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded