Download it now!
Bug 91983 - Manage changes does not follow changes to Style elements -- paragraph, character, page, etc.
Summary: Manage changes does not follow changes to Style elements -- paragraph, charac...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) Master
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
: 58725 128030 (view as bug list)
Depends on:
Blocks: Track-Changes
  Show dependency treegraph
Reported: 2015-06-10 12:17 UTC by V Stuart Foote
Modified: 2019-10-31 08:55 UTC (History)
7 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description V Stuart Foote 2015-06-10 12:17:55 UTC
The Manage Changes dialog does not correctly track changes to direct formatting (although bug 91838 suggests some formatting is tracked) nor to Style changes of paragraphs, characters, frames, pages, or lists.

Rather, it only reacts to textual changes in a document.

For tracking changes to be more useful, Manage changes at a minimum needs to follow paragraph and character style changes. Then perhaps any direct formatting within paragraphs. And finally all implemented styles that can end up in ODF.
Comment 1 Yousuf Philips (jay) (retired) 2015-06-11 11:22:57 UTC
I'm assuming this is a limitation of the current track changes implementation in ODF, which is currently being revamped.
Comment 2 Robinson Tryon (qubit) 2016-08-25 05:39:02 UTC Comment hidden (obsolete)
Comment 3 Heiko Tietze 2017-08-28 12:01:48 UTC
Currently the character style is tracked but not paragraph. The implementation wouldn't change workflow or visualization, so removing needsUX keyword.

Build ID: 9600f5179795380749aa5a7c9fa0bf5387d2b95f
CPU threads: 4; OS: Windows 6.1; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2017-08-27_23:19:54
Locale: de-DE (de_DE); Calc: group
Comment 4 Gabor Kelemen 2019-05-29 15:23:22 UTC
This is a duplicate of #58725 but since this one is more clearly worded, I'm marking that one as dupe of this.
Comment 5 Gabor Kelemen 2019-05-29 15:23:28 UTC
*** Bug 58725 has been marked as a duplicate of this bug. ***
Comment 6 Aron Budea 2019-10-31 08:55:48 UTC
*** Bug 128030 has been marked as a duplicate of this bug. ***