Description: The width of the image properties dialog box is displayed adapted to the content of the description. Steps to Reproduce: 1. Right click on an image. 2. Properties 3. Options tab 4. Type a multi-line description. 5. Confirm changes. 6. Click back in. Actual Results: Width of the image properties dialog box is displayed adapted to the content Expected Results: Normal width dialog box with the description displayed on several lines. Reproducible: Always User Profile Reset: Yes Additional Info: It happens since several versions ago but I don't remember when it started happening (if I remember correctly, since 7.0 or even earlier).
Created attachment 175461 [details] Long description
Created attachment 175462 [details] Short description NOTE: It does not matter if the text has spaces or not. It adapts to the length of a certain number of characters and then makes a line break.
Created attachment 175463 [details] Text with spaces Since instead of proving it they will say that it is because the first capture has no spaces, I show that it does not depend on the spaces between the words.
I can confirm with 7.3, it works in 6.0
This seems to have begun at the below commit. Adding Cc: to Matteo Casalin ; Could you possibly take a look at this one? Thanks cd6651803f018ec6334c7079ec1c10e8691a4996 is the first bad commit commit cd6651803f018ec6334c7079ec1c10e8691a4996 Author: Jenkins Build User <tdf@pollux.tdf> Date: Tue Jun 5 08:15:12 2018 +0200 source 565340d457f41197474a75ba1b036bdc3d569041 https://git.libreoffice.org/core/+/565340d457f41197474a75ba1b036bdc3d569041 Fix tdf#100937: LO Freezed when I insert a very long text in... ... the Description box The issue was triggered by ImpVclMEdit::Resize initially calling TextEngine::SetMaxTextWidth() with a negative width (due to an initial empty area, further "reduced" to take into account a vertical scroll bar) and then with positive values in following iterations. I preferred to consider such negative widths a no-op instead of extending them to the "maximum" possible width.
Dear Leandro Martín Drudi, 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