Description: When I set the description and comment text boxes for a report in the database, I found that the "Auto Grow" parameter can only be temporarily set to "Yes", and this parameter is automatically set to "No" immediately after saving the document, causing the long text to be cropped and not displayed as expected. Steps to Reproduce: 1) Enter a long text in the corresponding text box that it can be full in it; 2) Set "Auto Growth" of the corresponding text box to "Yes" in the corresponding report editing interface; 3) Save the document (maybe this step can be omitted); 4) Close the report editing interface; 5) Open the preview or view the text box "Auto Grow" status. Actual Results: Long text appears only within the text box set size and the text is cropped. Check the corresponding text box settings and found the "Auto Grow" parameter displayed as No. Expected Results: The height of the text box automatically becomes longer, the text is not cropped, the "Auto Grow" parameter is not automatically set to be "No" either. Reproducible: Always User Profile Reset: Yes Additional Info: [Information automatically included from LibreOffice] Locale: zh-CN Module: ReportDefinition [Information guessed from browser] OS: Windows (All) OS is 64bit: no
I could confirm the buggy behavior if the field, which is set to "Auto Grow" isn't the first field in a row. "Auto Grow" will be set to the value of the first field in a row. So you couldn't set one field to "Auto Grow" → "Yes" and other fields in the same row to "No". Value for the first field will be saved for all fields. This behavior appears since the function is implemented in LO 6.4. I see two possibilities to solve this bug: → When changing the value in one field a warning should appear and all fields should be changed. → Should be possible to set Auto Grow to only one field, not the others in one row. Tested with OpenSUSE 15.3 64bit rpm Linux. Doesn't work since LO 6.4.
This bug has already been reported: https://bugs.documentfoundation.org/show_bug.cgi?id=131664 *** This bug has been marked as a duplicate of bug 131664 ***