Bug 117473 - No Undo after updating Table of Contents
Summary: No Undo after updating Table of Contents
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: TableofContents-Indexes Undo-Redo
  Show dependency treegraph
 
Reported: 2018-05-07 09:53 UTC by zerebro
Modified: 2019-09-22 10:55 UTC (History)
2 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 zerebro 2018-05-07 09:53:36 UTC
Description:
Undo is working as long you do not update a ToC or Table of Figures. Undo history emptied. Button is then greyed out.
Later edits will be recorded as usual, undo possible again. 

Steps to Reproduce:
1.write - add header - add toc - write
2.undo (ok)
3.refresh toc
4.undo (impossible)

Actual Results:  
see above

Expected Results:
see above


Reproducible: Always


User Profile Reset: No



Additional Info:


User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.1 Safari/605.1.15
Comment 1 Dieter 2018-05-07 10:53:02 UTC
I confirm it with

Version: 6.1.0.0.alpha1+ (x64)
Build ID: 775d0f26beecffccf3ed27a6a011aff20d91f842
CPU threads: 4; OS: Windows 10.0; UI render: default; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-04-26_01:05:25
Locale: en-US (de_DE); Calc: CL

and also with 

Version: 4.4.7.2
Build-ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Gebietsschema: de_DE

Duplicate of bug 89611?
Comment 2 Aron Budea 2018-06-30 13:38:41 UTC
Same with 3.3.0, so a different issue than bug 89611.
Comment 3 QA Administrators 2019-07-01 02:46:29 UTC Comment hidden (obsolete)
Comment 4 zerebro 2019-07-31 11:48:30 UTC
Similar behaviour reported in Bugs 89611 and 119878 which are partly marked as "inherited from OOo".
Comment 5 zerebro 2019-09-22 10:55:18 UTC
Bug is not present in

Version: 6.3.1.2
Build-ID: b79626edf0065ac373bd1df5c28bd630b4424273
CPU-Threads: 4; BS: Mac OS X 10.12.6; UI-Render: Standard; VCL: osx; 
Gebietsschema: de-AT (de_AT.UTF-8); UI-Sprache: de-DE
Calc: threaded

Setting Status field to RESOLVED-WORKSFORME

Big thanks to whoever solved this!