Description: When a table has a sub-table that doesn't have "Allow row to break across pages and columns" set breaks over a page that has a footer, the footer will hide the row. (With the tick box set, it is harder to reproduce at times, but can still be done by setting both tables to have a repeating header) Steps to Reproduce: 1. Create a footer with some content 2. Create a table with 3 rows, 1 column, with a repeating header of first row. Allow it to split over pages. 3. Insert a line of text for header and first row 4. Insert a table in 3rd row, with 1 column and 3 rows, with a repeating header of 1st row. 5. Change this sub-table to not break rows over pages and columns. 6. Insert content for header row and content rows. 7. Add line breaks to start of document until table breaks over page. Actual Results: The second (and subsequent) content rows of the sub-table correctly break to the next page, with repeated headers for outer and inner table. When enough line breaks (or other content) is before the table so that the first content line and header of the sub-table should be pushed to next page, instead it is hidden by the footer row. Expected Results: The table should be pushed to the next page. (along with the outer-table row it is in) Reproducible: Always User Profile Reset: Yes Additional Info: Version: 5.4.3.2 (x64) Build ID: 92a7159f7e4af62137622921e809f8546db437e5 CPU threads: 4; OS: Windows 6.19; UI render: default; Locale: en-AU (en_AU); Calc: group User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Created attachment 137902 [details] Document before pushing over page
Created attachment 137903 [details] Document before pushing over page [PDF]
Created attachment 137904 [details] Document before triggering bug
Created attachment 137905 [details] Document before triggering bug [PDF]
Created attachment 137906 [details] Document showing bug
Created attachment 137907 [details] Document showing bug [PDF]
Created attachment 137948 [details] Screenshot showing different result from 3.6 vs. 6.0 3.6 does not hide the Header in the same step, but it does hide the "Content" in the previous step (of line breaks). Maybe it would be useful to bibisect it anyhow. Arch Linux 64-bit Version: 6.0.0.0.alpha1+ Build ID: 008673c23db0c812eb0b48a1c29ab88b48aaa867 CPU threads: 8; OS: Linux 4.13; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded Built on November 23rd 2017 Arch Linux 64-bit Version 3.6.7.2 (Build ID: e183d5b)
Tried bibisecting with bibisect-win32-5.4, but got a useless huge range. As the bibisecting targeted only one aspect of the problem, it would probably not have been very useful anyway.
Dear Kieran Grant, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Version: 6.2.4.2 Build ID: 2412653d852ce75f65fbfa83fb7e7b669a126d64 CPU threads: 16; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded
Version: 6.3.0.1 Build ID: 41ac97386aba908b6db860cfb4cfe2da871886ae CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: CL
Just tested on 6.4 line, and the problem is still there. But I did notice that if I add two more rows in the sub-table, it appears the bug only affects the sub-tables header row and first row, all subsequent rows correctly break over the next page. Version: 6.4.0.3 Build ID: b0a288ab3d2d4774cb44b62f04d5d28733ac6df8 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded
Created attachment 166608 [details] PDF showing that in 7.0.2.2 the situation has improved somewhat As of 7.0.2.2 the content rows now appear to push successfully, but the sub-table header row still is hidden. Version: 7.0.2.2 Build ID: 8349ace3c3162073abd90d81fd06dcfb6b36b994 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
Dear Kieran Grant, 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
Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 32; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded