Bug 135376 - Formatting messed up after undo (track & changes involved)
Summary: Formatting messed up after undo (track & changes involved)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Track-Changes Undo-Redo
  Show dependency tree / graph
 
Reported: 2020-08-02 08:38 UTC by Telesto
Modified: 2023-04-22 03:38 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Example file (631.43 KB, application/vnd.oasis.opendocument.text)
2020-08-02 08:38 UTC, Telesto 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-08-02 08:38:34 UTC 
Description:
Formatting messed up after undo (track & changes involved)

Steps to Reproduce:
1. Open the attached file
2. CTRL+A
3. CTRL+X
4. backspace backspace delete bullet)
5. CTRL+V
6. CTRL+Z
7. CTRL+Z
8. CTRL+Z

Actual Results:
Red formatted text

Expected Results:
Ideally not


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.1.0.0.alpha0+ (x64)
Build ID: <buildversion>
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: ru-RU (nl_NL); UI: en-US
Calc: CL

also in
6.4

6.1 6.2 crash
Comment 1 Telesto 2020-08-02 08:38:48 UTC 
Created attachment 163868 [details]
Example file
Comment 2 Telesto 2020-08-02 08:45:11 UTC 
@Michael Stahl
This another spin-off of bug 134746. Leaving it in the middle if this is worth investigating; Some say it isn't the case. I can't tell, leaving it up to the person who knows most about they undo stack & track changes
Comment 3 BogdanB 2020-09-18 20:51:44 UTC 
Confirm in
Version: 7.1.0.0.alpha0+
Build ID: d57b14e3394b081adf0888ed8dcb7b86d66c246c
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-US (ro_RO.UTF-8); UI: en-US
Calc: threaded
Comment 4 QA Administrators 2022-09-19 03:32:50 UTC 
Dear Telesto,

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 https://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://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug