In order to reproduce the bug: [1] Create new text document. [2] Enable Automatic Spell Checking: Menu > Tools > Automatic Spell Checking [3] Choose center alignment. [4] Insert a misspelt word. The word is underlined with a read wavy line. [5] Right click on misspelt word. A context menu is displayed with correction items. This is OK. [6] Right click right of misspelt word. A context menu with copy and paste and formatting items is displayed. This is also OK. [7] Right click and don't release mouse key left of misspelt word. The misspelt word is selected and the context menu with the correction items is displayed. Expected: Context menu like in step 6. [8] Release mouse key. The context menu is no longer displayed. Expected: Display of context menu like in step 6. The same bug also occurs if the text is right-aligned and also in tables with the respective alignements. Bug occurs in version 6.0.5 (64 bit, Win 10) The bug already exists in version 3.3.0. Hence inherited from OOo.
Hi Harald, I don't reproduce with LO 6.0.4.2 Build ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf Threads CPU : 2; OS : Windows 6.1; UI Render : par défaut; Locale : fr-FR (fr_FR); Calc: CL Same behavior when using Open GL.
Hi Jacques, I tested the function again with 6.0.5. The bug still exists. Perhaps step 2 may be a problem. You need not perform this step if Automatic Spell checking is already enabled. Furthermore at step 4 there is a mistake in my original description. Correct is: [4] Insert a misspellt word followed by a space. The word is underlined with a red(!) wavy line. Did you get this underlining?
My observation in 6.0.5 (I'm not sure, that it is the same you, Harald, describes): If mouse pointer is on the left of a misspelled word the context menu of spellchecking appears. If mouse pointer is on the left or above or below a mispelled word, the context menu with copy and paste appears. It doesn't matter if the cursor is before, after or within the word. I would expect, that context menu is the same, when Mouse pointer is right or left
Harald, Dieter, With LO 6.0.5.1 Build ID: 0588a1cb9a40c4a6a029e1d442a2b9767d612751 Threads CPU : 2; OS : Windows 6.1; UI Render : par défaut; Locale : fr-FR (fr_FR); Calc: CL I get same behavoir as in 6.0.4.2: At step 8, when I release mouse key, the context menu doesn't change. I can therefore finish the correction. The misspelled words are underlined too when Automatic Spell checking is set and I add a space at the end of a misspelled word If you get no change when using "Restart in safe mode...", I gess this is a Windows 10 only issue.
Created attachment 143283 [details] Image that shows the different context menus Opem the attachment. I expect that in case A (before misspellt word) the same context menu is displayed like in case C (after misspellt word). Only in case B the context menu with proposed corrections should be displayed.
Created attachment 143490 [details] Spell check not working even though it's on Showing that autospell is on; however, none of the jiberish is underlined.
I found something in 6.2.0.0. It is probably me and if so, I apologize for wasting your time. Spell check isn't working. I turn it on and turn it off and turn it on again. I type jiberish and nothing is getting underlined. I have an attachment showing that autospell is on and that no words in the document are underlined. Perhaps I am missing something. I'm writing this here because I found it when I went to test the bug in this report.
(In reply to Susan Gessing from comment #7) > I found something in 6.2.0.0. It is probably me and if so, I apologize for > wasting your time. Spell check isn't working. I remember, that spellcheck isn't implemented in LODev (But I'm not sure for 100%)
(In reply to Dieter Praas from comment #8) > (In reply to Susan Gessing from comment #7) > > I found something in 6.2.0.0. It is probably me and if so, I apologize for > > wasting your time. Spell check isn't working. > > I remember, that spellcheck isn't implemented in LODev (But I'm not sure for > 100%) One can always install https://extensions.libreoffice.org/extensions/english-dictionaries
Repro. Adding a bug to see also, although we might only need one of them... Arch Linux 64-bit Version: 6.2.0.0.alpha0+ Build ID: 860a9daf2b45942a4b10ff22d36aa3fe29be19f4 CPU threads: 8; OS: Linux 4.17; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded Built on July 14th 2018
Dear Harald Koester, 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 still exists with version 6.2.5 (64 bit, win10).
*** Bug 99568 has been marked as a duplicate of this bug. ***
Dear Harald Koester, 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