Bug 118419 - Wrong Context Menu Before Misspelt Word
Summary: Wrong Context Menu Before Misspelt Word
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 99568 (view as bug list)
Depends on:
Blocks: Context-Menu
  Show dependency treegraph
 
Reported: 2018-06-27 16:30 UTC by Harald Koester
Modified: 2021-05-16 17:26 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments
Image that shows the different context menus (90.18 KB, image/png)
2018-07-03 10:26 UTC, Harald Koester
Details
Spell check not working even though it's on (74.01 KB, application/vnd.oasis.opendocument.text)
2018-07-11 20:05 UTC, Susan Gessing
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Koester 2018-06-27 16:30:26 UTC
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.
Comment 1 Jacques Guilleron 2018-06-27 21:54:31 UTC
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.
Comment 2 Harald Koester 2018-07-02 08:50:08 UTC
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?
Comment 3 Dieter 2018-07-02 09:09:20 UTC
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
Comment 4 Jacques Guilleron 2018-07-03 00:31:09 UTC
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.
Comment 5 Harald Koester 2018-07-03 10:26:32 UTC
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.
Comment 6 Susan Gessing 2018-07-11 20:05:50 UTC
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.
Comment 7 Susan Gessing 2018-07-11 20:09:59 UTC
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.
Comment 8 Dieter 2018-07-12 07:39:54 UTC
(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%)
Comment 9 Buovjaga 2018-07-15 17:49:26 UTC
(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
Comment 10 Buovjaga 2018-07-18 13:17:54 UTC
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
Comment 11 QA Administrators 2019-07-19 02:53:37 UTC Comment hidden (obsolete)
Comment 12 Harald Koester 2019-07-23 11:38:09 UTC
Bug still exists with version 6.2.5 (64 bit, win10).
Comment 13 Harald Koester 2019-07-23 11:39:19 UTC
*** Bug 99568 has been marked as a duplicate of this bug. ***