Description: Undoing and redoing input of the last _two or more_ rows in a table in Impress slide results in last row drawn as single-line height, with additional lines hanging outside the table frame, IF AND ONLY IF the text in next-to-last row consists of single line, text in the last row is multi-line, and Undo is done after putting cursor to another row OR unselecting table and then entering any row (including the last one) again. Moreover, this is only the first of more shenanigans that can be done to the table in this state (see below). Steps to Reproduce: 1. Create or open new Impress presentation. [I use soffice.exe --impress] 2. Create a new slide. 3. Create a table using center-area menu, select 1 column and 2 or more rows. 4. Enter text row by row. Text in rows excluding the last two can be in single line or multiple lines. 5. Enter single line of text in next-to-last row. 6. Enter multiple lines in the last row. 7a. Put cursor to any other row OR 7b. deselect table, then select it again and enter any row. [This step is required because otherwise Undo deletes text of the last row word-by-word and the bug conditions are not met.] 8. Perform Undo at least twice. [I use Ctrl-Z] Note: after the first Undo, the last row will shrink to a single line. If you perform Redo right now, text and correct height of the last row is restored. 9. Perform Redo same numer of times as previous Undo. Actual Results: Last row remains drawn as single line. Other lines of text appear below the table frame. It's not just cell-shading issue, because the frame itself is drawn after the first line and can be interacted with. Additionally, if in this state you enter any row/ cell and move the cursor in it, height of the last row is restored instantly. However, steps 8 and 9 remain repeatable (see attachment). Expected Results: Height of the last row is restored to a correct number of text lines. Reproducible: Always User Profile Reset: No Additional Info: After clicking-down on the hanging text and dragging the table a bit (it is allowed to do so), more fun can be had with Undo/ Redo. At this state, results become a little unpredictable, but so far I managed: a) make Undo skip undoing the text insertion of the last row (the text in the previous rows get deleted and restored, while the last one remains) and b) make Impress _jump to the first slide_ each time Undo or Redo is performed, even if the second slide (the one with the table) is repeatedly selected in-between. Based on this experience, I think this bug is distantly related to Bug 89323 (see Comment 3 in that report). I can't reproduce the failure to delete table using Undo, but I strongly suspect Undo stack garbling happening here. Tables in Impress are evil. --- Version: 6.5.0.0.alpha0+ (x64) Build ID: a70c83f5881ec11def660a6158e04d9ec47207ef CPU threads: 8; OS: Windows 10.0 Build 18362; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: CL ---
Created attachment 156674 [details] Bug reproduction in pictures
It seems this started happening before the release of 4.2. Previously, undo had no effect at all! So I guess we are on the sunny side of history. I tested both on Win and Linux. Testers should keep in mind the step "7a. Put cursor to any other row".
Dear Stepas Toliautas, 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