Created attachment 125030 [details] page 4-7 Hello. It does not fix the correct location of objects. In MS Office & WPS office opens correctly. The LO 4.4.7.2 do not see pictures of the objects
Hi RomaNIck, Thanks for reporting. Confirmed in Version: 5.2.0.0.alpha1+ Build ID: 52871b360c73efd59bfbc811b8b89a02b6375b29 that the objects on page 4-7 are positioned in the wrong table cell. Can you maybe provide a screen shot of the correct situation? Ciao - Cor
Created attachment 125109 [details] WPS Office, analogously to MS
Relating frame position: Repro with: Version: 5.4.0.0.alpha0+ Build ID: 84f2ff67a7e404febf710b1dc7f66d06745c503f CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-12-09_23:20:01 Locale: nl-NL (nl_NL); Calc: CL Position of frame with the table seems quite good in: LibreOffice 3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b I also created a new bug report related to the inconsistent pie chart color (bug 104579)
tables position regression introduced by: author Cédric Bosdonnat <cedric.bosdonnat@free.fr> 2013-02-20 10:04:16 (GMT) committer Cédric Bosdonnat <cedric.bosdonnat@free.fr> 2013-02-20 10:17:00 (GMT) commit d0cde9640b52ccfbb28ed1f65bba0927afd7b69b (patch) tree 18c6342798d98ff8559a3cf26dac4994a2f82998 parent a633a96c3a50d803e5fa43b603edc0b8e2e34b6e (diff) n#779642: Fixed floating tables import in writerfilter
Still reproducible in Version: 6.0.0.0.alpha0+ Build ID: bde72cdae1e7e001d5089c5284672c976b8e43df CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group
Hi Tamás, This issue was introduced by the same commit that introduced bug 109053, which was recently fixed by you in commit fc55711f01af172eb3a034454405fa941454c781. Would you mind taking a look at it when you have some spare time ? Regards
(In reply to Xisco Faulí from comment #6) > Hi Tamás, > This issue was introduced by the same commit that introduced bug 109053, > which was recently fixed by you in commit > fc55711f01af172eb3a034454405fa941454c781. Would you mind taking a look at it > when you have some spare time ? > Regards Hi Xisco, There is an ugly hack in the code related to tables. Sometimes tables are imported as simple Writer tables, sometimes as a table inside a text frame (called floating table). The second one is used to workaround the missing features of Writer tables compared to Word tables. It's not something I can fix easily. For bug 109053 it was easy to avoid this floating table stuff and import the table as simple a Writer table, but otherwise it's hard to handle this kind of bugs. So I would not dig myself in this problem now.
** 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
Repro 6.3+. Can be a duplicate of Bug 80869.
The issue is still reproducible in Version: 7.0.0.0.alpha0+ Build ID: 11e6582b23b983fde4b04ece5b37c546bcd98a43 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded but it improved after https://cgit.freedesktop.org/libreoffice/core/commit/?id=4d5c0eaf3e0d3d3bcd9e691fffee19b75f3d6631 @László Németh, I thought you might be interested in this issue...
It looks to me like this is simply using the wrong anchoring. It should be relative to the cell margins, but it is being positioned relative to the page. NISZ guys have been going some work in this area, but this document isn't fixed yet in 7.1+.
(In reply to Justin L from comment #11) > It looks to me like this is simply using the wrong anchoring. It should be > relative to the cell margins, but it is being positioned relative to the > page. NISZ guys have been going some work in this area, but this document > isn't fixed yet in 7.1+. Those are floating tables inside non-floating ones and the automatically added frame has wrong anchoring. We did not dare to touch such... yet.
Dear RomaNick, 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
Miklos, the attached file with float table crashes LO in current master. I think it's one from crashes after your great float table work.
I hope to get to this in the near future.
The crash was fixed by 7.6 commit 1795d5183d5371a24e8dcb15f8671c78b2c94665 Author: Miklos Vajna on Fri Apr 28 08:28:22 2023 +0200 sw floattable, crashtesting: fix PDF export of tdf114111-3.docx The document looks pretty good now. There are what look like image size problems - where the image/wrapping is too large to fit in the expected cell, and so extra white space is seen.
Looking at the first chart on page 4, that also crosses the vertical cell border between A1 and B1 in Word. But their chart background is transparent, while in LO the chart area is filled with white. As an additional data point, binary DOC does the same in Word, so old Word used to have white background, now it's transparent, but Writer even has it as white today. Looks like a chart problem, not a DOCX / floating table problem by now, as the metabug would suggest.