I am currently editing a document in Hebrew (originally created in Word, i.e. imported at some point), and making many changes - to the text, the indentation and the numbering. I'm noticing that, occasionally, the changes I make stop appearing, and in fact, a chunk of text - it seems to be the entire current paragraph I'm changing - disappears. When I re-enable viewing the tracked changes - the paragraph is still not there. It's not marked as deleted - it is wholly missing, and cannot be restored even when I try to Undo my last actions. The undo buffer seems to get emptied. Unfortunately I cannot attach the document to help with reproducing this issue because it's too private.
I'm marking this as blocking RTL-CTL, even though I'm only guessing that it has something to do with the RTL direction.
I'm marking this as blocking RTL-CTL, even though I'm only guessing that it has something to do with the RTL direction. Also, I believe the loss only happens when I make deletions or overwrites, not additions. And it is certainly not consistent, i.e. most deletions and overwrites do work.
Seeing this now also with the LO 7 release version: Version: 7.0.0.3 Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e CPU threads: 4; OS: Linux 5.2; UI render: default; VCL: gtk3 Locale: he-IL (en_IL); UI: en-US
> Also, I believe the loss only happens when I make deletions or overwrites, > not additions. And it is certainly not consistent, i.e. most deletions and > overwrites do work. Maybe it's actually an "Undo" operation rather than a deletion.
Thnaks for reporting the bug. Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem. Please provide a clearer set of step-by-step instructions on how to reproduce the problem. And I also think tat we need an example document. => NEEDINFO
(In reply to Dieter from comment #5) I understand. Unfortunately, I can't share the specific document I used; and the behavior was not consistent and predictable enough to enable me to replace the confidential text with other text. I will just have to ask you to rely on my experience as a long-time "QA contributor" for LO, to believe my report and trust that the bug actually exists...
(In reply to Eyal Rozenberg from comment #6) > I will just have to ask you to rely on my experience as a long-time "QA > contributor" for LO, to believe my report and trust that the bug actually > exists... I believe you, but it's also a basic rule in LO, that someone else has to reproduce the bug until status can be set to NEW. One solution would be to send this document in private, but we also need some reliable steps to reproduce.
(In reply to Dieter from comment #7) Since I don't have reliable reproduction steps - keeping it as UNCONFIRMED is a reasonable solution (as opposed to closing...) Thanks again.
Resolving for now, since I'm not seeing it with many other documents (even though I've not been doing exactly the same kind of heavy track-changes work). Will re-open if I see this again.