Steps to reproduce: 1. Write a sentence as so: Why is *CMD-I to turn on italics* thhis *CMD-I* not working? 2. Right click on thhis and choose to correct to 'this' 3. Italicized formatting is lost Current behavior: In most situations, the italics formatting is preserved. However, there seem to be a few isolated cases where it is lost. Expected behavior: In all cases where formatting is initially present formatting should be preserved after a spelling correction has been performed. Platform (if different from the browser): os x 10.7.4 $ java -version java version "1.6.0_33" Java(TM) SE Runtime Environment (build 1.6.0_33-b03-424-11M3720) Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03-424, mixed mode) Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.56 Safari/536.5
(In reply to comment #0) > Current behavior: > In most situations, the italics formatting is preserved. However, there seem > to be a few isolated cases where it is lost. Checked with: LO 4.0.0.2 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit Could not reproduce. What are those "isolated ones"? Do you have any Steps To Reproduce this every time?
(In reply to comment #1) > (In reply to comment #0) > > Current behavior: > > In most situations, the italics formatting is preserved. However, there seem > > to be a few isolated cases where it is lost. > > Checked with: > LO 4.0.0.2 > Build ID: own W7 debug build > Windows 7 Professional SP1 64 bit > > Could not reproduce. > What are those "isolated ones"? Do you have any Steps To Reproduce this > every time? Nope. Sorry, I tried to generate exact steps, but the precise combination eluded me. I just noticed that if I did the steps many times, at some point a word or two would lose the formatting. I know it's an imprecise bug, and if no one else is experiencing this significantly it's probably not worth the time. I would only see the behavior about once a week
I also was unable to reproduce, without a test case and/or explicit steps that always result in problem not much we can do. Marking as WFM @Hamilton - thanks for taking the time to report, feel free to reopen if you figure out how to consistently trigger. Furthermore * * results in bold not italicized....
Created attachment 123019 [details] Document with reproducible case I am attaching a sample document where correcting spelling removes format. There are two bold words. The first one is misspelled. Correcting it removes the bold format. The second one, if changed to be misspelled and then corrected, does not lose the bold format. Tested under: * Windows 10, LibreOffice 4.4.2.2 * Ubuntu Trusty, LibreOffice 5.0.4.2 (5.0.4~rc2-0ubuntu1~trusty1 from Ubuntu LibreOffice PPA) * Debian Sid, LibreOffice 5.1.1.1 (5.1.1~rc1-1 from official Debian repos) Hope this helps.
NEW per comment 4.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
Problem still occurs. Version: 5.4.0.2 Build ID: 1:5.4.0~rc2-1 CPU threads: 4; OS: Linux 4.2; UI render: default; VCL: gtk3; Locale: en-US (en_US.utf8); Calc: group
Created attachment 136638 [details] Expanded test set (21 test cases) for this issue, proving reproducibility
This is actually reproducible! Whenever the formatting is applied to the space after the misspelled word, formatting is modified / lost. I have attached another document with 21 cases tested divided in three sections: (a) formatting applied is italics, (b) formatting applied is regular (non-italics using direct formatting) and (c) italics removed. In the three sections the behavior follows the same pattern: good/bad/good/bad/bad/good/good. I have not tested what happens if the space after has different formatting but this should be enough to prove reproducibility of the bug. From the tests, the failing cases should not be at all uncommon.
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Reproducible. Version: 6.1.1.2 Build ID: 1:6.1.1-1 CPU threads: 4; OS: Linux 4.2; UI render: default; VCL: gtk3; Locale: en-US (en_US.utf8); Calc: group threaded
Dear Hamilton Turner, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
*** Bug 135867 has been marked as a duplicate of this bug. ***
Cannot reproduce this issue with Version: 7.1.0.0.alpha0+ Build ID: a06a83b29a9da770787bffe416b138102aa12531 CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: de-AT (de_AT.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-08-24_01:03:26 Calc: CL Can anybody confirm that too?
Seems to be working indeed Version: 7.1.0.0.alpha0+ (x64) Build ID: 8700bace8c0714d853f5df6918ab9c8bb3d81f77 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 Or should I say for the examples proposed here.. the duplicate has the same bug.. but still having the quirk
(In reply to Telesto from comment #15) > Seems to be working indeed > Version: 7.1.0.0.alpha0+ (x64) > Build ID: 8700bace8c0714d853f5df6918ab9c8bb3d81f77 > 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 > > Or should I say for the examples proposed here.. the duplicate has the same > bug.. but still having the quirk Then the duplicate shall live and this one shall die. Make it so!
I can reproduce the issue in the test document of bug 135867 with LibreOffice 5.0.6.3 but NOT with the daily build from today. So that the other one is a duplicate of this bug is still true.
*** Bug 99786 has been marked as a duplicate of this bug. ***
Still reproduced in 7.0 with the sample from Comment 4. Example from bug 99786 is also reproducible in release: Version: 7.0.0.3 Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e CPU threads: 4; OS: Mac OS X 10.13.6; UI render: default; VCL: osx Locale: en-US (en_RU.UTF-8); UI: en-US Calc: threaded But nightly works for me.
*** Bug 104137 has been marked as a duplicate of this bug. ***
Possibly fixed with patch for bug 135721 from Michael Stahl. Will be part of LibO 7.1.0, 7.0.2 and 6.4.7. We should test LibO 7.0.2 and 6.4.7 as well when they're ready and also the other bugs of meta bug 127250 (Formatting-Text-Diverse) - [META] Text formatting issues when inserting or overwriting.
(In reply to Thomas Lendo from comment #22) > Possibly fixed with patch for bug 135721 from Michael Stahl. > Will be part of LibO 7.1.0, 7.0.2 and 6.4.7. > > We should test LibO 7.0.2 and 6.4.7 as well when they're ready and also the > other bugs of meta bug 127250 (Formatting-Text-Diverse) - [META] Text > formatting issues when inserting or overwriting. https://dev-builds.libreoffice.org/daily/libreoffice-7-0/current.html https://dev-builds.libreoffice.org/daily/libreoffice-6-4/ Dates on the latest builds look like they should all contain the fix. Windows build of 6.4.7 is not so sure, because the build broke at the same day the patch landed.