Description: Redo changes text in superscript Steps to Reproduce: 1. Open the attached file 2. Place the cursor at the end of the line 3. Press backspace (until everything is gone 4. Type something: say BBBBB 5. Press and hold CTRL+Z 6. Press and hold CTRL+Y Actual Results: Superscript text Expected Results: Same formatting as initially Reproducible: Always User Profile Reset: No Additional Info: Found in Version: 7.1.0.0.alpha0+ (x64) Build ID: abcc4eb907661e07ad850ccce7eb06f129da4286 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL and in 4.4.7.2
Created attachment 165604 [details] Example file
And in LibreOffice 3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b
I can't confirm with Version: 7.1.0.0.alpha1+ (x64) Build ID: f27c4ec5c864395f4cdaec32d7e95ff24e4f43c8 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: threaded
Created attachment 166766 [details] Screencast
(In reply to Telesto from comment #4) > Created attachment 166766 [details] > Screencast I've followed steps, but can't reproduce it.
Reproduced on master build as of today. The issue seems to be that there is a superscript within the paragraph (i.e., the "st" after the word "1st"), and at the time of pressing UNDO and REDO, at a specific point Writer has messed up with superscript and normal chars.
Telesto, please retest, it seems the bug is gone. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5e7327e9313e2d9fe2f0defb30d3e7dc28c0b2ce CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
Sorry, the bug still here, with video steps. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5e7327e9313e2d9fe2f0defb30d3e7dc28c0b2ce CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
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