Created attachment 128796 [details] blank_edit_topTables.pdf: shows regression - rows are too thin / frames are not equal heights In attachment 99125 [details] from bug 78756, the two boxes at the top of the page should be roughly equal. However, due to a regression in 4.4, the right-side box is smaller than it should be. In the top-right hand table, the second column is blank. In the first column, the font size was changed from the default style's 14 to 10. The second column should be using the default size of 14 - thus making each row taller. (ignore the fact that the table below is pushed over top of these boxes - that is bug 78756.) Using Linux bibisect-44max, the regression was found to be caused by https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-3-5&id=705a8c226aee3e68db492083b7cf8b704335328b commit 705a8c226aee3e68db492083b7cf8b704335328b Author: Caolán McNamara <caolanm@redhat.com> CommitDate: Wed Sep 24 10:04:48 2014 +0100 WW8PLCFMan::AdjustEnds deeply flawed concept wrt change tracking
Setting this bug as NEW as the commit that introduced the regression has been identified Adding Cc: to Caolán McNamara
Created attachment 128836 [details] TwoPageTable.doc: simple unit test - should be two pages long.
Created attachment 129096 [details] Bold and Italic not imported in this file Another file affected by the same commit. In this case, the title Johnston Franklin should be italic and bold
Created attachment 131087 [details] Meeting or Workshop Attend sheet.doc: another doc affected by the same commit. The problem here is in the line containing the text: Dates covered by the Meeting/workshop. The font switches to Comic Sans MS (the default style's font), but it should be Abyssinica SIL.
Created attachment 131088 [details] Meeting or Workshop Attend Sheet Word2007.png: layout with table positionng properties shown (In reply to Justin L from comment #4) It appears that the floating table was "defined" somewhere in relation to the line with the problematic font. (In LibreOffice, the floating attribute is removed, and the NB line is placed underneath the table instead of above - which is why I suggest that the table is anchored in that line.) That suggests that Caolan's comment https://bugs.documentfoundation.org/show_bug.cgi?id=102334#c6 probably applies to this document also.
(In reply to Justin L from comment #5) > That suggests that Caolan's comment > https://bugs.documentfoundation.org/show_bug.cgi?id=102334#c6 probably > applies to this document also. I think I properly reverted that old 2011 commit in testing, and it did not resolve the font problem. Reverting the 2014 regression mentioned in the description however DID resolve the problem.
Created attachment 131200 [details] tdf103967_minimal.doc: minimal version of doc from Comment 5
Giving up on this one. I think the "regression" commit is OK, but probably there is table-related code somewhere that fudges the character attribute start position which needs to be updated to match the new code.
*** Bug 111802 has been marked as a duplicate of this bug. ***
Justin, bug 111802 regressed at the same commit, and its bugdoc (attachment 135545 [details]) has no tables, maybe that's easier to work with.
Created attachment 137302 [details] Floating Font Size Example REDLINED.doc: modified test from bug 135545 (In reply to Aron Budea from comment #10) > Justin, bug 111802 regressed at the same commit, and its bugdoc (attachment > 135545 [details]) has no tables, maybe that's easier to work with. Thanks, but still failed since my redlined version of the test still has an extra large paragraph. But maybe this is better than nothing: + else if (&rDesc == m_pChp && rDesc.nEndPos == m_nLineEnd && rDesc.nEndPos > rDesc.nStartPos && !HasCharSprm(NS_sprm::sprmCDttmRMarkDel).pSprm) + rDesc.nEndPos--; // ... then shorten by one character
** 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
Dear Justin L, 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://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
Dear Justin L, 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