I have a multi-page table, with Heading rows repeating at the top. On one of the pages, the letters on the bottom row of the table are getting cut off below the bottom of the page boundary. See screen shot.
Steps to Reproduce:
1.I wasn't able to reproduce. After exiting Writer and re-opening the document, the table row CORRECTLY appeared at the top of the next page. It appears some flow and refresh logic isn't happening correctly.
Text on bottom row is getting cut off below the bottom page margin
Row should get bumped to next page if it doesn't fit inside the page margin.
User Profile Reset: No
Version: 188.8.131.52 (x64)
Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1
CPU threads: 4; OS: Windows 10.0; UI render: default;
Locale: en-US (en_US); Calc: group threaded
Created attachment 145082 [details]
Created attachment 145083 [details]
I can't confirm it with your document and
Version: 184.108.40.206.alpha0+ (x64)
Build ID: 62cd86977ca41677c56fb2d1f97bb1c5cbdbd416
CPU threads: 4; OS: Windows 10.0; UI render: GL;
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-09-20_02:34:32
Locale: en-US (de_DE); Calc: CL
Build ID: 76bf3939b0583212a56c317c85aea110f8ac6fee
CPU threads: 4; OS: Mac OS X 10.12.6; UI render: default;
TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-07-27_06:01:47
Locale: nl-NL (nl_NL.UTF-8); Calc: group threaded
Build ID: 8a35821d8636a03b8bf4e15b48f59794652c68ba
1. Open the attached file
2. Scroll down to page 38
3. Press Enter before "Hop" after Appendix A
4. Content moves to the next page (with layout similar to the screenshot)
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!
Opened a newer version of the same file in Windows 220.127.116.11 x64. In the affected table. it is CORRECTLY pulling "U.S. Hallertau" to the top of the next page now. See new screen shot
Created attachment 154398 [details]
6.3.0 screen shot
I also added a blank line in a table cell ABOVE "U.K. Kent GOldings", and it CORRECTLY pulled that row to the top of the next page.
Was there an intentional patch for this, of dumb luck that it seems to be fixed for this document?
(In reply to Andrew from comment #9)
> I also added a blank line in a table cell ABOVE "U.K. Kent GOldings", and it
> CORRECTLY pulled that row to the top of the next page.
> Was there an intentional patch for this, of dumb luck that it seems to be
> fixed for this document?
Set status to RESOLVED WORKSFORME because of comment 9