Summary: | Multi-column text frame in footnote at end of document will not wrap or break text to the second column | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | William Friedman <will.friedman> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | normal | CC: | buzea.bogdan, telesto |
Priority: | medium | ||
Version: | 6.4.5.2 release | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 103164, 107656 | ||
Attachments: |
Video demonstrating the problem
File where you can see the problem Before After |
Description
William Friedman
2023-10-13 18:37:39 UTC
Created attachment 190199 [details]
Video demonstrating the problem
Here is a video demonstrating the problem. (My apologies for the weird format, but it does open in VLC.)
Created attachment 190200 [details]
File where you can see the problem
Here also is the file I used to test. You can see the problem by switching between Footnote position "end of page" and "end of document."
A few more things:
* I tried it for endnotes, and the send problem happens. (I guess the title description should be broader.)
* In the video I set the frame to anchor "as character" but using the other settings doesn't affect the problem.
Could it be related to the various limitations met in Endnotes? Endnotes page style cannot be configured for multi-column (setting is ignored). Also page breaks are ineffective. Created attachment 190285 [details]
Before
Created attachment 190286 [details]
After
Hello William, I was able to reproduce the bug using the steps you described, also on MacOS: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Mac OS X 14.0; UI render: Skia/Metal; VCL: osx Locale: en-US (en_RO.UTF-8); UI: en-US Calc: threaded Besides your steps I did some further investigations that might be helpful for having a better overview of this bug. (The following tests except the last one, were executed on the configurations listed above) 1. Instead of ‘Relative to Entire paragraph area’ width (step 3) a. I did set it to ‘Relative to Entire page with an 80% percentage -> The behavior was the same b. I also left the ‘Relative to’ unchecked -> the result was the same c. And I also checked the AutoSize checkbox and created the Frame in that way - > The behavior was the same —> Which means that these variables(‘Relative to’ and ‘AutoSize’) are not influencing the results nor does the value of the width. 2. I did try to reproduce the bug with a Frame that has 3 columns instead of two -> The behavior was the same -> Any number of columns greater than one returns the same result 3. I added data in both columns before changing the Position of the Footbar from ‘End of the Page’ to ‘End of the Document’ and what I observed was that the data from column2 is transferred on a new row to the colum1, and even if the cursor is able to go to column 2 area, once the user types some characters, the characters are displayed in column 1 so the column 2 becomes unusable and the frame acts like it has just one column even if 2 columns can be seen. Please check the screenshot attached. ('Before', 'After') 4. Regarding the documentation, I read the Footnote & Endnote chapter but I couldn’t find anything related to the Footnotes having any limitations on Frames. The documentation that I read can be found at this link: https://documentation.libreoffice.org/assets/Uploads/Documentation/en/WG7.6/WG76-WriterGuide.pdf 5. Tried to reproduce the bug on other types of documents in LibreOffice (Calc Spreadsheet, Impress Presentation, Draw Drawing, Math Formula and Base Database) but none of them offers the possibility of adding a footnote or a frame so the bug is Writer Document specific 6. I wanted to see if this issue is a new one or it can be found also on older versions of the app and it seems like it can be reproduced also on version: 6.4.5.2 - 2020 —--> So it doesn’t seem to be a new issue. I also tried older versions (4.0.0.1, 5.0.0.1 and 6.0.0.1 but they are not compatible with my OS and the app didn’t open so I can’t say if the issue is not older than 6.0.0.1) Hope my additions are helpful and let me know if something is unclear and needs clarification. Bianca, thank you. I think you now need to set the bug status as "new", right? (We're not supposed to change the status of our own bugs.) |