Description: Hi, I found that there is an error when table is nested. You could easily see the bug in attachment. I debug the code, and I know there is bug with SwTabFrame::MakeAll(), but the layout algorithm is too complex for me to fix it. Is there any one could help fix this. Thanks. :D Steps to Reproduce: 1.set page width to 8 cm and page height to 6 cm 2.insert a table with 2 rows and 1 column. 3.insert a inner table with just one cell into first table's bottom cell. 4.set the inner table border color to cyan to more easily see the layout bug. 5.enter 7 empty lines in to inner table. 6.enter empty lines into outer table to make the upper cell's bottom line strictly close to the page bottom. sadly, the whole inner table which should at second page goes totally into first page. Actual Results: Looks like following first page ------------------------------------------------------------------- | | | | | | | | |-----------------------------------------------------------------| | all inner table content goes here with less than 0.2 cm height | |-----------------------------------------------------------------| second page Expected Results: first page ------------------------------------------------------------------- | | | | | | | | |-----------------------------------------------------------------| | inner table at second page | | | | | | | | | |-----------------------------------------------------------------| Reproducible: Always User Profile Reset: No Additional Info: Version: 4.3.3.2 Build ID: ab5787d23cc2fddf057ced56647ef9f5e6ebefdd
Created attachment 146613 [details] the odt to reproduce the bug
Created attachment 146614 [details] the normal layout
Created attachment 146615 [details] the layout with error
Created attachment 146616 [details] the expected result
I can't confirm this with Version: 6.2.0.0.alpha1+ (x64) Build ID: 8274c4c62df5b937b3f0bec9e1eeca85f3b219d4 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-22_01:47:50 Locale: en-US (de_DE); Calc: CL
Comment on attachment 146613 [details] the odt to reproduce the bug Well, you could see the layout is in error status just directly open the attachment "error_layout_with_nested_table.odt" without any operation. My bug description's step is base on an empty document. I will check it first anyway.
(In reply to Dieter Praas from comment #5) > I can't confirm this with > > Version: 6.2.0.0.alpha1+ (x64) > Build ID: 8274c4c62df5b937b3f0bec9e1eeca85f3b219d4 > CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; > TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-22_01:47:50 > Locale: en-US (de_DE); Calc: CL Well, you could see the layout is in error status just directly open the attachment "error_layout_with_nested_table.odt" without any operation. My bug description's step is base on an empty document. I will check it first anyway.
(In reply to 564398053 from comment #6) > Comment on attachment 146613 [details] > the odt to reproduce the bug > > Well,My bug description's step is base on an empty document. > > I'll reupload the attachment and Reproduce step with images. > You could see it. > Thanks
Created attachment 146639 [details] Open this file, and press enter as what attachment's images do
Created attachment 146640 [details] step 0, open the attachment odt
Created attachment 146641 [details] step 1, press enter at this position
(In reply to 564398053 from comment #8) > (In reply to 564398053 from comment #6) > > Comment on attachment 146613 [details] > > the odt to reproduce the bug > > > > Well,My bug description's step is base on an empty document. > > > > I'll reupload the attachment and show reproduce step with images. > > You could see it. > > > > Attachments done. Please check it again, thanks.
(In reply to 564398053 from comment #12) > (In reply to 564398053 from comment #8) > > (In reply to 564398053 from comment #6) > > > the odt to reproduce the bug > > > > > > Well,My bug description's step is base on an empty document. > > > > > > I'll reupload the attachment and show reproduce step with images. > > > You could see it. > > > > > > Attachments done. Please check it again, thanks.
(In reply to Dieter Praas from comment #5) > I can't confirm this with > > Version: 6.2.0.0.alpha1+ (x64) > Build ID: 8274c4c62df5b937b3f0bec9e1eeca85f3b219d4 > CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; > TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-22_01:47:50 > Locale: en-US (de_DE); Calc: CL Sorry for making the comments so dirty. Please Check attachments again. I upload a new one, the old is obsolete. As described in attachment's images you could soon reproduce the bug. Thanks.
Repro Version: 6.2.0.0.alpha0+ 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
Also reproduced in Version: 5.2.0.0.alpha0+ Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53 Threads 4; Ver: 4.10; Render: default; Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
@Mike Kaganski, I thought you could be interested in this issue...
Still exists in version Version: 6.3.0.0.alpha0+ (x64) Build ID: 0f25a3c36f27fd51453b9a9115f236b83c143684 CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-27_20:06:55 Locale: zh-TW (zh_TW); UI-Language: en-US Calc: threaded Thank you!
Dear 564398053, 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