Bug 47688 - Handling of "Record changes", "Show changes" and save status inconsistent
Summary: Handling of "Record changes", "Show changes" and save status inconsistent
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.1 release
Hardware: All All
: lowest minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Track-Changes
  Show dependency treegraph
 
Reported: 2012-03-21 19:21 UTC by Matthew Francis
Modified: 2022-05-02 14:40 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Francis 2012-03-21 19:21:46 UTC
The interaction between changing "Record changes","Show changes" and the document saved status is inconsistent.

For instance, with a new document:

Initial status:
Record changes=NO  Document changed=NO

Enable record changes
Record changes=YES  Document changed=YES

Save document
Record changes=YES  Document changed=NO

Type "A"
Record changes=YES  Document changed=YES

Disable record changes
Record changes=NO  Document changed=YES

Undo
Record changes=NO  Document changed=NO

---

After the last action, the "A" has been untyped, and record changes remains off, but the document is inconsistent with the saved copy (in the saved copy "Record changes" is ON, whereas in the open copy it is OFF but the document is marked unchanged)

The same applies to "Show changes".
Comment 1 Joel Madero 2012-12-08 00:12:06 UTC
I was able to verify this. 

Just a note for developers, it's the undo that's causing weird stuff (clearly a change to document but it's not showing (ie you can't just do ctrl+s))

Marking as:
New (confirmed)
Minor (Doesn't prevent high quality professional work)
Lowest (very specific situation, if a user typed one thing later they wouldn't even notice it)

Thanks for the report, verified on 3.6.3.2
Comment 2 QA Administrators 2015-01-05 17:52:00 UTC Comment hidden (obsolete)
Comment 3 Matthew Francis 2015-01-29 08:56:52 UTC
Still occurs in OSX 10.10 / LO 4.4.0.2
Comment 4 QA Administrators 2016-02-21 08:36:48 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2017-03-06 15:38:17 UTC Comment hidden (obsolete)
Comment 6 Xisco Faulí 2022-05-02 14:40:31 UTC
Dear László Németh ,
This bug has been in ASSIGNED status for more than 3 months without any
activity. Resetting it to NEW.
Please assign it back to yourself if you're still working on this.