Created attachment 183690 [details] Cell A1 no longer splits when containing a section Version: 7.4.3.2 Build ID: 40(Build:2) CPU threads: 4; OS: Linux 6.0; UI render: default; VCL: kf5 (cairo+xcb) Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded Example use case (a bit contrived): creating a choir programme Data is by essence tabular regarding the singers: 4 categories S A T B, leading "naturally" to a 4-column table. Each cell contains a heading (Soprano, Alto, Tenor, Bass) followed by the list of singers. Some voices may have more participants than others. In order to give a more balanced aspect to the table, some voices may be listed 2-column. The solution of a nested table is not optimal because 1) this data is not "tabular", it is an alphabetical sequence, 2) splitting must be done manually which complicates changes in the list. A 2-column section is inserted below the cell heading for the list. The list is automatically balanced. But, the cell size no longer automatically expands once it has reached bottom of page though text flow property has been set at "Allow row to break". The section is still laid out as expected in some intermediate buffer and its columns are clipped to cell size. This is visible in cell A1 of the sample file. Worse: implementation could limit clipping and break disabling to the "sectioned" cell but adjacent cell B1 which contains a long comment does not split either without containing a section. The red overflow triangle is not shown in both cells. Cells in row 2 have no section and behave as usual. Additionally, manual column break is ineffective though menu Insert>More Breaks>Manual Column Break is not disabled. A cell is a variable-sized sub-document where the equivalent of page break is both the cell limit (when row height is manually set) and the "split-break" caused by the underlying page break. Then a manual column break should be possible. The bug has two visible consequences: - column break is computed as if the cell could expand indefinitely (probably up to page height) and section contents is then clipped to cell real size - section disables row split (probably because the concept of column break is not well defined in the context of a "container", table or frame)
Created attachment 183789 [details] screenshot of selected overflowing text in section (LO 7.4.3) Reproduced in: Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: de-DE (en_AU.UTF-8); UI: en-US Calc: threaded Two-column section's text overflows and is "hidden" outside the table cell, which does not split to the next page to accommodate text. Changing Format > Sections > Options > Columns to 1 single column does split the contents across two pages. Undoing the operation two go back to 2 columns results in a split section that looks different to the original.
Already an issue in: Version: 6.3.6.2 Build ID: 2196df99b074d8a661f4036fca8fa0cbfa33a497 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; Locale: de-DE (en_AU.UTF-8); UI-Language: en-US Calc: threaded
Dear ajlittoz, 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
Bug still present in 24.8.3.2