Description: Sometimes – I don't know why – one or two rows of a table stop being vertically centered, even though they're set to behave this way. The table corrects itself when clicking on the bugged row or when doing big edits in a document (deleting headings or adding/deleting multiple rows of text). I still consider this a somewhat important bug as it seems somewhat random to me. This is a problem because it might mean that someone is working on a big project, while the document keeps changing behind his back. Also, when exporting the .odt-file as a PDF, the non-centered-ness still get's ported over. Steps to Reproduce: 1. Open the .odt file I have attached. 2. Scroll down towards the 3rd white table-row. 3. See bug: The 10 (and the "SA, Studenten; Ein Gespräch.") isn't centered. Those two cells are the ones that are supposed to be vertically centered. Actual Results: The 10 (and the "SA, Studenten; Ein Gespräch.") isn't centered. Those two cells are the ones that are supposed to be vertically centered. When the bug occurred to me, two or three rows were off-center. Unfortunately, I corrected them (by clicking on them) and saved the document. Well, it happened again. Expected Results: This should just never happen. Table cells that are set to be (vertically) centered should stay centered. Otherwise, LO might be messing up documents behind a users back. Reproducible: Always User Profile Reset: Yes Additional Info: I tested on both Windows (LO 7.0.1.2) and on Linux (LO 7.0.2.2). Here's the data from Linux Mint 20: Version: 7.0.2.2 Build ID: 8349ace3c3162073abd90d81fd06dcfb6b36b994 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: de-AT (en_GB.UTF-8); UI: en-GB Flatpak Calc: threaded Also, on Windows, I tested on both Word and LO. Word opened the files correctly (actually, when I tested the whole thing, i used a .docx-file, but the bug seems to also be present on .odt) Seeing as how MS Word seemed to handle this file just fine, this is probably a LO-Bug and has little to do with the actual file. I might be wrong about that though.
Created attachment 166529 [details] Bugged .odt-file
Created attachment 166530 [details] PDF of the bugged .odt-file
Created attachment 166531 [details] xml-export of the bugged .odt-file I couldn't find any clues what could have caused this in the .xml file but someone more experienced might.
Cannot confirm. The 10 (and the "SA, Studenten; Ein Gespräch.") isn't centered because that row is divided between pages. If you delete text above, it centers. MSO behaves the same as LO for this row. Change could be requested, but I wouldn't support it. So please clarify. DOCX is another issue.
> (In reply to Timur from comment #4) Thank you for testing, there's a few misunderstandings however: > The 10 (and the "SA, Studenten; Ein Gespräch.") isn't centered because that > row is divided between pages. As far as I can tell, this is not true. I'm not sure how you got that information, but here are two reasons why it shouldn't be due to the row being divided across pages: 1. In the exact same layout (meaning the 10-row is split between pages), I had BOTH the 10-row and the 45-row stuck in this state. Thus, it can't be just be the page break. (actually, the 45-row was the only off-centered one. 10 was fine.) 2. Something to easily test: a. Open the .odt b. Look at the 10-row. It should be vertically misaligned. c. Click somewhere inside the 10-row. The row should correct its alignment. This happened without you deleting stuff. The 10-row still is split. The text became centered though. Thus, it can't be the page-break that's responsible. > If you delete text above, it centers. Yes, but as shown in my previous point, this doesn't mean what it might seem to show. > MSO behaves the same as LO for this row. I assume MSO means Microsoft Office? In my tests, MSO DIDN'T behave as did LO. In MSO, the 10 actually was vertically centered. In LO, the 10 was vertically misaligned. > So please clarify. Did my answers make sense? Also, I do not support setting this to a low-priority issue. Tables morphing behind your back isn't a minor thing to happen and it makes LibreOffice and the files it exports seem unprofessional. (LO is amazing though, which is why this is unfortunate)
Created attachment 166787 [details] .odt in MSO 2016 and LO 7.1+ We don't see the same, here is comparison of MSO and LO. Let's wait next opinion.
Clarc: which version of MS Office do you use?
(In reply to Timur from comment #6) > Created attachment 166787 [details] > .odt in MSO 2016 and LO 7.1+ > > We don't see the same, here is comparison of MSO and LO. Let's wait next > opinion. That picture shows EXACTLY what I was talking about! Look at the 10 and at "SA, Studenten; Ein Gespräch." On the left side (MSO) they are vertically centered. On the right (LO) they cling to the top, which is what my bug-report is all about! Also, thank you for uploading that comparison. It's a great picture, that helps illustrate the bug. (In reply to Buovjaga from comment #7) > Clarc: which version of MS Office do you use? When I tested, i did so on a Laptop I didn't own. Give me a few hours to check the version. Also: 1. Why is the MS Office-version relevant? 2. As stated previously, the Screenshot Timur posted perfectly showed the bug. I feel like there's some confusion about what i was talking about when filing this bug... Is anything unclear?
(In reply to Clarc from comment #8) > 1. Why is the MS Office-version relevant? > 2. As stated previously, the Screenshot Timur posted perfectly showed the > bug. I feel like there's some confusion about what i was talking about when > filing this bug... Is anything unclear? Right, I do see what you mean now, so Timur actually confirmed -> NEW MSO versions behave differently and are not compatible with each other in various ways.
(In reply to Buovjaga from comment #9) > Right, I do see what you mean now, so Timur actually confirmed -> NEW Not sure if he intended to confirm, but his screenshot clearly shows the bug. > MSO versions behave differently and are not compatible with each other in > various ways. I'll post it in a few hours, as soon as I get access to that PC. Also, I'm not a 100% sure "Table Rows aren't vertically centered, when split across two pages" is the correct Title for this bug. As I previously mentioned, the row starting with "45" used to be misaligned as well, in the same position. It shouldn't just be the split row. I suggest reading my replies to Timur to get a clearer picture of how this bug works if you didn't already do so.
Okay, so I have some more information. I stubled over a different version of the same document, and we can use it to mess up more rows. Here is how to get multiple misaligned rows: 1. Download "Bugged .odt-File 2222" and open it. The "10" and the "SA, Studenten; Ein Gespräch." should be misaligned. 2. Now slowly delete the footnote. As more and more table-rows move to the first page, they too start being misaligned. WHAT THIS MEANS: 1. It's not the page-break that keeps those rows stuck in the vertically misaligned position. If you save the document and reopen, all 3 rows will still be misaligned, not just the first one. 2. The page-break may however trigger that change in the first place. I changed the title accordingly. . . . (In reply to Buovjaga from comment #7) > Clarc: which version of MS Office do you use? Windows: "Version 2009 (Build 13231.20418 Klick-und-Los) Android: 1.0.1 On both of them the Table gets displayed correctly. It's only LO (and maybe OpenOffice) that display (and export to PDF) the file incorrectly.
Created attachment 166822 [details] Bugged .odt-File 2222
Dear Clarc, 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 bug still is present. The initially attached document still contains the bug. The attachment of comment https://bugs.documentfoundation.org/show_bug.cgi?id=137612#c6 contrasts the bug with how the document looks in MS Word. Comment https://bugs.documentfoundation.org/show_bug.cgi?id=137612#c11 nicely highlights how to reproduce the bug yourself. Version: 7.4.2.3 / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Flatpak Calc: threaded
*** Bug 154130 has been marked as a duplicate of this bug. ***
Thanks. The bug still is present in Version: 7.5.1.2 (X86_64)
The bug still is present in Version: 24.0.0.2 (x86_64) / LibreOffice Community Build ID: b1fd3a6f0759c6f806568e15c957f97194bbec8f