Description: Paragraph Direct Formatting bold lost after rejecting changes Steps to Reproduce: 1. Open the attached file 2. Place cursor and the end of the document 3. So after the 'tab' behind version 4. Press and hold backspace until top of the page (you will notice version changing formatting) (from text body to Chapter 2) 5. Now reject everything (Paragraph Direct Formatting, bold gone for Version Actual Results: Paragraph DF gone after reject changes Expected Results: Still present Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 2bb10a827ac13d0caf009e8526ccd9f17dc71653 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 Jumbo
Created attachment 178403 [details] Example file
Found in Version: 6.2.9.0.0+ (x86) Build ID: 5f01fe15eb2661f1f9ce12d1d99dc2a705b462ee CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL not in 6.1 Bibisect with environment variable SW_REDLINEHIDE
@Luke Only to
Reproduced in Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 6961f6732954742415413fa53bdeebd1b03d9ec5 CPU threads: 8; OS: Linux 5.16; UI render: default; VCL: gtk3 Locale: zh-CN (zh_CN.UTF-8); UI: zh-CN Build Platform: Fedora34@X64, Branch:master, bibisect-linux-64-7.4-CN Calc: threaded Fedora 34. Set to NEW.
I don't see this happening before 6.4. In 6.3 and before the Reject all did not bring back the empty paragraph and the Version paragraph. Bibisected: the bold DF disappearing after Backspace all + reject all in 6.4 since: https://git.libreoffice.org/core/+/dc9a0b124272a6dc0a8d875d51b6f882e60a8a04 author László Németh <nemeth@numbertext.org> Wed Aug 07 11:25:13 2019 +0200 committer László Németh <nemeth@numbertext.org> Fri Aug 23 11:25:14 2019 +0200 tdf#127101 Change tracking: reject format at paragraph join Adding CC to: László Németh
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
repro 26.2+