Description: Wrong formatting when typing (like track & changes involved) Steps to Reproduce: 1. Open attachment 164521 [details] 2. Edit -> Track changes -> Accept all changes (but only to show it's even present after Accept all; only in that sessions) File reload and issue goes away 2. Start typing (don't move the cursor first) -> Green Actual Results: Green font Expected Results: Black font 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: nl-NL (nl_NL); UI: en-US Calc: CL not in Version: 6.4.0.0.beta1+ (x64) Build ID: 20be5cd0bdc57d812bf34a2debfe48caa51de881 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: GL; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL
Telesto: The test document has track-changes enabled, so we you type in the document it is in track-changed mode. This is expected. Am I missing something? Set to NEEDINFO. Please set back to UNCONFIRMED after you have provided clarification.
(In reply to Kevin Suo from comment #1) > Telesto: > The test document has track-changes enabled, so we you type in the document > it is in track-changed mode. This is expected. Am I missing something? Yes, the changes are tracked, but they aren't shown, that setting is turned off. Plus shown tracked edit is shown in yellow color. What I see is that the font at that point is set to Lime color, however for me that difference persist back until 6.0, and it's black in 5.4. Telesto, are you sure the color is black as you would've expected in 6.1-6.4?
I skipped step 2, since as I understand that isn't necessary. The bug started with the following commit, bibisected to its 6.0 backport using repo bibisect-linux-64-6.0. Adding CC: to Michael Stahl. https://cgit.freedesktop.org/libreoffice/core/commit/?id=1c8efde4daea648204e3ba19f8edc01ef3e548bd author Michael Stahl <mstahl@redhat.com> 2018-02-14 12:57:49 +0100 committer Michael Stahl <mstahl@redhat.com> 2018-02-15 09:56:55 +0100 tdf#83260 sw: call CompressRedlines() in ODF import
Created attachment 173157 [details] Screenshot of the example file with changes visible What happened here is that the text was deleted from the lower "Les algorithmes" paragraph backwards to the upped "Les Algorithmes" paragraph, which has the green color direct formatting. This makes the bullet of the "Les Algorithmes" paragraph retain its direct formatting, so if you start typing after it, you get the green color of the bullet.
Created attachment 173163 [details] Simplified example file without change tracking This file shows that the behavior documented here is not specific to change tracking. To test: highlight the text from the paragraph marked with B. to the beginning of A. (which is green) then press Delete. Start typing: the text is now green too. In fact this behavior was ever present way back to 3.5. Since 6.0 the change tracking scenario follows this, before it did not follow. We can argue whether this behavior is desirable (Word for example would let to delete the first bullet and apply all the formatting of the second), but I don't think there is a change tracking regression.
Created attachment 173164 [details] The change tracking free document before deleting from B. to A.
Created attachment 173165 [details] The change tracking free document after deleting from B. to A. and typing a bit
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