If Track Changes is set, deleting a word by continuous backspaces or deletes, results in separate undo actions for each letter.
Steps to Reproduce:
1. Open a Writer document.
2. Insert a word or a few words, say "Hello World".
3. Turn on Track Changes
4. Delete a word, say "World", by hitting Backspace for each letter.
5. Now pressing Ctrl-Z only restores the last letter, in this case, "W", instead of the whole word.
A new undo action is added for each letter.
The undo actions should be grouped to form a single undo action.
User Profile Reset: No
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
Since you changed to Assigned and confirmed the bug yourself, I change back to Needinfo.
Why do you think it's a bug?
If we delete letter by letter, then Undo restores letter by letter.
If we delete word by word, then Undo restores word by word.
Looks logical. MSO works the same.
So I set the importance as "medium enhancement". Does that solve the problem?
It's not importance that was my question, but why do you think that actual results are wrong.
On a second thought, you may be right. There's a single reject action and undo action could be single. As it was before like in OO and LO 3.3, looks like regression all the way from 3.4.
I set back to Assigned.
This bug report is about using the same grouping mechanism for delete undo actions irrespective of whether Track Changes is set or not set. Are you sure this is a regression?
Created attachment 134864 [details]
Test with LO 3.3
Looks like regression because it worked as expected with OO and LO 3.3, as attached.
(In reply to Timur from comment #5)
> Created attachment 134864 [details]
> Test with LO 3.3
> Looks like regression because it worked as expected with OO and LO 3.3, as
I am trying to provide a better solution for bug 107340. FYI bug 107340 has not been marked as a regression yet.
For more details, please check https://gerrit.libreoffice.org/#/c/39472/ and https://gerrit.libreoffice.org/#/c/40166/
Since it is not within my scope to fix the regression, I removed myself as Assignee.
** 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!