Created attachment 185580 [details] Page when I save document (content masked) I have 25 tables in document, remove one of them, save document. Then I quit LO Writer. Next time I load document I have to scroll through whole document and check did any table reappeared in document. As EMPTY one. Then I have to remove them. And check whole document layout again. And repeat on each document load. Or copy/paste everything to fresh one.
Created attachment 185581 [details] Same page when I load document after saving (content masked)
I have spent half a day on copying text from one file to another just to have document without removed tables. And then had to remove one. Which made my attempt to have working file worthless.
Please attach an example document. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Please provide every step how did you delete your table? Like 1. Select all table using icon on the Table toolbar 2. Press Delete key on the keyboard or 1. Select all table using holded Shift key and cursor keys on the keyboard 2. Delete table using icon on the Table toolbar
(In reply to Roman Kuznetsov from comment #4) > Please provide every step how did you delete your table? > > Like > > 1. Select all table using icon on the Table toolbar > 2. Press Delete key on the keyboard > > or > > 1. Select all table using holded Shift key and cursor keys on the keyboard > 2. Delete table using icon on the Table toolbar LMB click on table, RMB to open context menu, Remove->Table option clears table, second Remove->Table removes it.
(In reply to Buovjaga from comment #3) > Please attach an example document. > Set to NEEDINFO. > Change back to UNCONFIRMED after you have provided the document. Sanitized version of document does not reproduce. I suspect that my bugs are connected with changes tracking enabled.
[Automated Action] NeedInfo-To-Unconfirmed
László has been making many fixes and improvements to change tracking regularly, so would be interesting to hear, if you reproduce the problem with the latest unstable https://dev-builds.libreoffice.org/daily/master/current.html If the bug still exists, then the next step would be to check, if a code change causing it can be found: https://wiki.documentfoundation.org/QA/Bibisect Unfortunately it can take dozens of gigabytes of disk space in order to investigate. I am available for helping with the process via screensharing.
Created attachment 185602 [details] Document to reproduce bugs 153818, 153816, 153817 This document reproduces bugs #153816, #153817, #153818 Information how it was created are inside of document. Changes tracking is enabled so you can check how it went.
sorry, forgot to unmark NEEDINFO
(In reply to Marcin Juszkiewicz from comment #9) > Created attachment 185602 [details] > Document to reproduce bugs 153818, 153816, 153817 > > This document reproduces bugs #153816, #153817, #153818 > > Information how it was created are inside of document. Changes tracking is > enabled so you can check how it went. What I'm seeing in this document currently is that - If I delete the first table, it is not deleted completely, but it leaves behind one row and I have to delete again - After saving and reloading, the table does not reappear. However, it is shown in the Navigator. This change of behaviour happened in 7.4 with 794fd10af7361d5a64a0f8bfbe5c8b5f308617a5, tdf#147347 sw: hide deleted table at deletion in Hide Changes. The previous commit crashes when trying to delete the remainder of the first table. I had to do lots of 'git bisect skip' due to this and a state, where it refused to delete it at all. I finally looked at the results of 'git bisect visualize' and did a range query in cgit.freedesktop.org and eyeballed interesting commits (from about 150 commits). Let's ask László what he thinks. I won't change the status as I'm unsure of what is going on here.
*** Bug 154195 has been marked as a duplicate of this bug. ***
The problem, which resulted by the transition to tracked table and table row deletion and insertion, fixed in the newer versions. A workaround for the affected versions is to disable change tracking temporarily during table deletion. I will check the last 7.4 bug fix release, which are the remaining problems there.