Created attachment 128666 [details] Test file for docx (table witjh page break) LibreOffice does not open the *.doc file containing a table and page breaks correctly. The *.docx can not be opened correctly. This is a split of the docx version from the bug #91799. ----------------------------------------------------------------- Here the comment4 bug #91799 again: Yes, it is broken when compared with Word viewer. LibO shows empty first page and the row heights in the table on the 2nd page are off. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: d28102b1ed0c31500bbc68453a7b7613bd2bfa06 TinderBox: Win-x86@39, Branch:master, Time: 2015-06-09_01:06:39 Locale: fi-FI (fi_FI)
Here comment 8 of bug #91799 again: DOCX shows empty table in LibO. DOCX table shows content in A1-A3 in Word Viewer. Win 7 Pro 64-bit Version: 5.3.0.0.alpha0+ Build ID: 7da2f3ce9f7b049c177a735a146dae84a764d3f7 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-10-04_03:49:06 Locale: fi-FI (fi_FI); Calc: CL LibreOffice 3.5.0rc3 Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735
NEW as I confirmed it.
Still reproducible in Version: 6.0.0.0.alpha1+ Build ID: 38a8157d9447134913d88c6c373d99a7aa472857 CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group
** Please read this message in its entirety before responding ** 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
still repro in Version: 6.2.0.0.alpha1+ Build ID: 6896f39ffd8a6c4b32b8f601a6a93678247456bd CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2018-11-05_22:40:18 Locale: ru-RU (ru_RU); Calc: threaded LibreOffice Writer shows a table on first page (and there is only one page in document in LO), but there isn't second page with table
This looks like the DOCX counterpart to bug 48097
Since the DOC counterpart was set as a duplicate of bug 108233, lets do the same for this one since apparently the ODF standard allows for something like this. *** This bug has been marked as a duplicate of bug 108233 ***
(In reply to Justin L from comment #7) > Since the DOC counterpart was set as a duplicate of bug 108233, lets do the > same for this one since apparently the ODF standard allows for something > like this. > > *** This bug has been marked as a duplicate of bug 108233 *** I'm not sure about that, this bugdoc in Word has two floating tables incorrectly separated, while the other bugs have one table separated with page breaks.
T(In reply to NISZ LibreOffice Team from comment #8) > I'm not sure about that, this bugdoc in Word has two floating tables > incorrectly separated... Well, Word is the definitive source and it says that it should be separated. So the separation in this particular case is correct. When bug 108233 allows LO to specify a page-break on a row, then we will be able to fix that. So you are correct, this should be a depends on instead of duplicate.
Dear m_josenhans, 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
The error remains in Libre Office version from my Linux distribution KDE Neon. Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 2; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE Flatpak Calc: threaded
Note that in LO 7.6 this document loses the first table based on commit ce3308a926f036b87515b8cd97d2b197063dc77a Author: Miklos Vajna on Wed Apr 12 08:13:07 2023 +0200 tdf#61594 sw floattable: import floating tables as split flys by default Miklos is actively looking for and fixing these edge cases, so a simple CC is adequate at this time.
Yes, this bug is on my list to look at once crashtesting looks better, which is the current burning fire.
This also has a Section break (Next page) on the first page, like bug 137859 and bug 150769
repro - first table still lost.
(In reply to Justin L from comment #15) > repro - first table still lost. Let me look at this.
Miklos Vajna committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/e2f90d1d0e51c68dd01c9968cdb7a3bbb5658613 tdf#103869 sw floattable: fix lost table right before a section break from DOCX It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.