Steps to reproduce: 1. Create new document in Writer and write or paste some text here. 2. Select a word and insert a comment on it. 3. Turn on change tracking. 4. Select a piece of text which *contains* the commented word and delete that piece. 5. Save the document. 6. Make any (small) change in the text. 7. Repeat steps 5 and 6 several times. Current behavior: On the first saving, the commented word (being part of the deleted text) becomes grayed (like a field). With subsequent modifications and savings, the grayed region changes randomly. Expected behavior: Obvious. This bug especially causes trouble when one gets to further editing in the affected region, or to undo, accept/reject change etc. Sometimes it tells me I cannot edit it because it is read-only.
With LibreOffice from the 43all bibisect repository, version latest, I see that the deleted word retains its reverse-image highlight across multiple saves including a couple of times when I closed and reopend the file.
for me not reproducible with LO 4.3.2.2 (Win 8.1)
Reproduced using steps provided by Jan. Grey space has erratic functionality and sometimes prevents edits stating it is read only. Setting status to NEW. Thanks! Version: 4.2.6.3 Build ID: 420m0(Build:3) OS: Ubuntu 14.04.1 x64
I can't confirm the random changes to the commented word. I can confirm the grey highlighting of that word after it has been deleted, crossed out by the change recording. This persisted over several saves. When I saved, the grey would go away temporarily and come back before I could do anything. If I edited the commented word (adding letters), the grey highlighting went away and did not recur. LO Writer 4.3.2.2 Win 8.1
Thank you for your replies and sorry for the long delay, I was too busy. This bug seems to have had been fixed earlier than I reported it. I have added the LibreOffice PPA to my repositories, so now I have LO version 4.3.3.2. I have not been doing any complex editing with comments and change tracking since the update, but my simple test case now works correctly. Also your comments suggest it has been fixed in 4.3. Thank you again.
Per last comment.