Bug 157371 - Frame auto-size ignores content after 1st line-break (Shift-Enter, see comment 5)
Summary: Frame auto-size ignores content after 1st line-break (Shift-Enter, see commen...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Frame
  Show dependency treegraph
 
Reported: 2023-09-21 23:08 UTC by Jim Avera
Modified: 2025-10-06 03:11 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
frametest.odt (17.45 KB, application/vnd.oasis.opendocument.text)
2023-09-21 23:08 UTC, Jim Avera
Details
screenshot.png (117.29 KB, image/png)
2023-09-21 23:10 UTC, Jim Avera
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Avera 2023-09-21 23:08:32 UTC
Description:
A frame with the Width set to "AutoSize" expands to match only the first line of content.  If a line-break is present the frame ignores the width of subsequent lines (so they don't fit if the first line is narrower than later lines).


Steps to Reproduce:
Open attached "frametest.odt", or:

1.In Writer, Insert->Frame->Frame... and 
     Check Width "AutoSize" 
     Set the minimu width to 0.02"
  
2. In the frame, type "X<line-break>YYYYYYY" (Control-Enter to enter line-break)

Actual Results:
The frame is only wide enough for a single "X" character, not "YYYYYYY"

Expected Results:
Resize the frame so the maximally-wide line fits


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: e472b5b557d2b43b41e488c83db2b188de499610
CPU threads: 12; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 1 Jim Avera 2023-09-21 23:08:55 UTC
Created attachment 189746 [details]
frametest.odt
Comment 2 Jim Avera 2023-09-21 23:10:20 UTC
Created attachment 189747 [details]
screenshot.png
Comment 3 Buovjaga 2023-10-03 15:49:09 UTC
Works fine for me with kf5 and gtk3. Could it have been some issue in master that got fixed after you tested?

Arch Linux 64-bit, X11
Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 6d57c8f4bbfb4bee20ad2581b2b65d8e31af4fbf
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 3 October 2023
Comment 4 Jim Avera 2023-10-04 22:42:20 UTC
@Buovjaga - I still see the same results (frame is only wide enough for the first line, not the widest line) in master build downloaded today.  Identical results as with 7.5.6.2.   

Would you please attach a screenshot of what you see when opening the "frametest.odt" file?   Is the frame wide enough for the "BBBBBBBBBB" line to not wrap?

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: f95c3994f0b6a82a3bc2ddfb68822b74479ae185
CPU threads: 12; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 5 Jim Avera 2023-10-04 23:08:28 UTC
There was a MISTAKE in original the "Steps to Reproduce".  You should type SHIFT-Enter (not Ctrl-Enter) to insert a line-break.   Using Ctrl-Enter starts a new paragraph, which is not the bug condition.

You can also do Insert->More Breaks->Manual Break... Line Break.

My apologies.  

(P.S. I wish Calc and Writer used the same keyboard shortcut for inserting line breaks!)
Comment 6 QA Administrators 2023-10-05 03:20:11 UTC Comment hidden (obsolete)
Comment 7 Buovjaga 2023-10-06 13:00:01 UTC
Thanks, repro already in oldest of Linux 43all bibisect repo.
Comment 8 QA Administrators 2025-10-06 03:11:47 UTC
Dear Jim Avera,

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