Created attachment 198525 [details] correct behaviour In Writer, when placing the visual cursor at the beginning of a misspelled word, the context menu (SHIFT+F10) does not always show the spelling suggestions. See attchted pics. If the word is preceded by a tab, it does. If by a space, it does not. If the cursor is moved one letter to the right from that start of the word, it behaves correctly. The previous version I was using, 7.6.7.2, did not exhibit this problem. Tested using clean profile. Currently using, Version: 24.8.4.2 (X86_64) / LibreOffice Community Build ID: bb3cfa12c7b1bf994ecc5649a80400d06cd71002 CPU threads: 12; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster; VCL: win Locale: en-AU (en_AU); UI: en-GB Calc: CL threaded
Created attachment 198526 [details] wrong behaviour
Please attach a sample file, and detail the step to reproduce the issue.
(In reply to m_a_riosv from comment #2) > Please attach a sample file, and detail the step to reproduce the issue. No need for a sample file. You can reproduce it very easily, 1. type two misspelled words, separated by a space. 2. move visual cursor to the start of the 1st misspelled word. 3. Press SHIFT+F10, corrections ARE presented. 4. Move visual cursor to the start of the 2st misspelled word. 3. Press SHIFT+F10, corrections ARE NOT presented. If the space between the words is replaced with a tab, it works for the second word as well.
Works for me. Version: 24.8.4.2 (X86_64) / LibreOffice Community Build ID: bb3cfa12c7b1bf994ecc5649a80400d06cd71002 CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
(In reply to m_a_riosv from comment #4) > Works for me. > Version: 24.8.4.2 (X86_64) / LibreOffice Community > Build ID: bb3cfa12c7b1bf994ecc5649a80400d06cd71002 > CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 26100); UI render: > Skia/Vulkan; VCL: win > Locale: es-ES (es_ES); UI: en-US > Calc: CL threaded Don't know what to tell you. Just installed it in a clean VM and the behavior is exactly the same. Version: 24.8.4.2 (X86_64) / LibreOffice Community Build ID: bb3cfa12c7b1bf994ecc5649a80400d06cd71002 CPU threads: 2; OS: Windows 11 X86_64 (10.0 build 22621); UI render: Skia/Raster; VCL: win Locale: en-AU (en_AU); UI: en-US Calc: threaded
Created attachment 198574 [details] Animation of behavior so there is no confusion
Again, attach a sample file showing the issue.
Created attachment 198578 [details] Sample file
Created attachment 198590 [details] Screnshoot, properties with 7.6.7
Works for me as expected. LO 24.8.4.2 OS: MacOS 15.2 Locale: en-US (en_FI:UTF-8); UI: en-US
Created attachment 198753 [details] works as it should
Hello Jordi, Thank you for reporting the bug. I can confirm that the bug is present in master. Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a8ec21adf255b70bb6eeb0a1717190df303d8b26 CPU threads: 12; OS: Windows 10 X86_64 (build 19045); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_FI); UI: en-US Writer: threaded
Noticed that hardware/OS was set to x86-64 (AMD64)/Windows (All) Please be advised that this also happens on Linux as well. Attaching animation showing the same behavior. Tested on, Version: 24.8.4.2 (X86_64) / LibreOffice Community Build ID: bb3cfa12c7b1bf994ecc5649a80400d06cd71002 CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
Created attachment 199000 [details] Animation of behavior on Linux
(In reply to Jordi from comment #14) > Created attachment 199000 [details] > Animation of behavior on Linux Bibisected with linux-64-24.8 to 5bc7d0186d1a70990377a2f4c630fe11e2dfd166 tdf#111969 sw: acknowledge that last half-character in Get*Correction
I can't reproduce this either in my Ubuntu 24.04's LO (which is 24.2). I used comment 8's LO 24.8.4.2 Tests.el.odt. (It works at the start of a word, but not at the end of a word.) However, I can reproduce this with my development builds. (It works at the end of a word, but not at the start of a word.)
(In reply to Justin L from comment #16) > I can't reproduce this either in my Ubuntu 24.04's LO (which is 24.2). Duh: first affects 24.8... and the Collabora Office I tested was also 24.2 based.
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/793853fbd1665e90ab91e9b45826174707617275 tdf#164703 tdf#111969 sw Get*Correction: only mouse passes PixelPos It will be available in 25.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Fix verified, thanks.
Thanks Justin. I assume you can now resolve as "fixed"?
(In reply to Stéphane Guillou (stragu) from comment #20) > Thanks Justin. I assume you can now resolve as "fixed"? After backports are completed...
Justin Luth committed a patch related to this issue. It has been pushed to "libreoffice-25-2": https://git.libreoffice.org/core/commit/5a6a6c146f3bd5d12d5426e64a49c2dc18028f5e tdf#164703 tdf#111969 sw Get*Correction: only mouse passes PixelPos It will be available in 25.2.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Justin Luth committed a patch related to this issue. It has been pushed to "libreoffice-24-8": https://git.libreoffice.org/core/commit/0be2539f57599f33efb8b542faf4a4d3762ba1e4 tdf#164703 tdf#111969 sw Get*Correction: only mouse passes PixelPos It will be available in 24.8.6. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.