Red underlinings of the spell checker are displayed in the print preview - Open writer - Turn on spell checker - Enter some spelling mistakes - Open the print preview
I fail to reproduce, tested using Linux Mint 16 x64 with LibreOffice Version: 4.1.5.3 Build ID: 410m0(Build:3) @OfficeUser: what OS do you use? Kind regards, Joren
I see it on both Linux and Windows platform. Maybe it is a regression. According to your comment you are using an old build. I have attached a screen shot.
Created attachment 97069 [details] bug
Reproduced with LibO 4.2.2.1 on Win7.
Do you have Field Shadings enabled (View -> Field Shadings). It appears that messing with that settings during a LO session allows me to reproduce this bug for some reason, as mentioned in bug 78112. Should that bug be marked a duplicate of this, since this is slightly older? Also, if this is the same bug, I've been able to reproduce this bug with every version I have access to, including OpenOffice 3.2.1, which predates LibreOffice. In that case, the version should be set to "Inherited from OpenOffice," since it's the first version the bug can be confirmed in. Also, that means that it's not technically a "regression," since it has never actually worked properly in LO. I can confirm that this bug, but only after messing with "Field Shadings." After that, the only way I've found to disable the red squigglies in my preview window is to close LO and restart it. Confirmed using LO 4.0.2.2 under 32bit Fedora 17 LO 4.2.5.2 under 32bit Fedora 17 OO 3.2.1 under 64bit RHEL6
"I can confirm that this bug, but only after messing with "Field Shadings." After that, the only way I've found to disable the red squigglies in my preview window is to close LO and restart it." I can exactly reproduce this with: Version: 4.2.4.2 Build-ID: 63150712c6d317d27ce2db16eb94c2f3d7b699f8 Strange is the fact that I never had used field shadings before. So there may other causes too that let me found this bug as I have reported it...
** 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 (4.4.1 or later): 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-07-18
Bug still exists in build 4.4.2.2.
Migrating Whiteboard tags to Keywords: (bibisectRequest) [NinjaEdit]
*** This bug has been marked as a duplicate of bug 78112 ***