Created attachment 174343 [details] Highlighted word with track changes enabled When a word is highlighted with track changes enabled, rejecting the recorded change does not remove the highlight. Adding the highlight again and rejecting it again removes it. Steps to reproduce: 1. Enter some text in a new document 2. Enable change tracking 3. Double click a word, set character highlight on it 4. Reject the change in the Manage Changes dialog Actual results: The word is still highlighted. Expected results: The word should not be highlighted. LibreOffice details: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: dd3ab0fd737ff84657ff34eebafe2628f489e5a1 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: CL But not yet in bibisect-7.3 repo from 6 days ago: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: da40449dc5f1841ac3e6f6aa1194834a363455b6 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: default; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: CL This is likely a side effect of the fix to bug 50447
Created attachment 174344 [details] Highlighted word after the tracked change was rejected
We have noticed that this does not happen on Linux. Strange... redlining should not be platform-specific.
Dear NISZ LibreOffice Team, 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