1) Open a document with structure that is fine for the creation of a TOC
2) Add the TOC
3) Notice that the Undo is active
4) Right-click > Edit Index/Table
5) Goto column tab and set it to 2 columns and press OK
6) Notice that the Undo is now inactive
This is a regression as this worked correctly in 3.3.0.
Build ID: 4cf69df2f543b023f4ec3d4279c5ac11a2a819d9
TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2015-02-21_03:46:34
Reproducible with LO 184.108.40.206, Win 8.1
(In reply to Jay Philips from comment #0)
> This is a regression as this worked correctly in 3.3.0.
Might not be bibisectable, but will need to check to be sure
Whiteboard -> bibisectRequest
Confirm that this works in 3.3.0 on OSX, but it's already broken in 220.127.116.11, so preBibisect
Reproduced this in the latest release 18.104.22.168
Reproducible with the latest nightly build of LibreOfficeDev 22.214.171.124.alpha1.
Migrating Whiteboard tags to Keywords: (preBibisect)
The "undo" history is also lost on an update of any index (TOC, Illustration Index, Index of Tables, etc.), either via its context menu or Tools -> Update -> Update All.
The issue could lead to a data loss, if one wishes to return to a previous, unsaved document state.
i disagree that clearing the Undo history should be considered dataLoss
- by that logic, every crash would be a dataLoss too, and we'd need
a new keyword for the i-load-a-file-and-store-it-and-oops-my-text-is-gone
(In reply to Michael Stahl from comment #8)
> i disagree that clearing the Undo history should be considered dataLoss
> - by that logic, every crash would be a dataLoss too, and we'd need
> a new keyword for the i-load-a-file-and-store-it-and-oops-my-text-is-gone
I don't now. One could argue that it's worse than a crash in terms of data loss. Because in the case of a crash there are recent backups which can be restored on the next start. While with this issue, one would need to purposely crash LO to get to those. A normal user would not know that - they would just consider the data lost. And the backups would be purged on the next regular LO shutdown.
But this might be another duplicate of the bug 38703.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
*** Bug 119878 has been marked as a duplicate of this bug. ***