Autocorrect (Word completion) doesn't work on Windows 11 testet with new Libreoffice versions:7.5.5 and 7.6.0. On Windows 10 systems autocorrect instead works without problems.
Please test in safe mode, Menu/Help/Restart in Safe Mode
Noop safe mode doesn't work either
I guess you have it enable Tools → AutoCorrect → AutoCorrect Options → Word Completion If not, please, test copying the profile from win10 to win11 for the same version. https://wiki.documentfoundation.org/UserProfile#Default_locations
of course, word completion is active Has to due with some kind of formating element, the suggestions are highlighted in yellow and for me seems, that this element no longer works on Windows 11. The wordbook autofills all kind of words written but can't propose them.
[Automated Action] NeedInfo-To-Unconfirmed
(In reply to HK from comment #4) > of course, word completion is active > Has to due with some kind of formating element, the suggestions are > highlighted in yellow and for me seems, that this element no longer works on > Windows 11. The wordbook autofills all kind of words written but can't > propose them. Can you tell more about this "formatting element"? I don't understand what you mean by it. Maybe you can attach an example document?
Created attachment 189762 [details] autocomplete how should work In the image you can see how autocoplete shoult work, it make a yellow proposal, on Windows 11 machines i don't see this proposal "element"
(In reply to HK from comment #7) > Created attachment 189762 [details] > autocomplete how should work > > In the image you can see how autocoplete shoult work, it make a yellow > proposal, on Windows 11 machines i don't see this proposal "element" Works fine for me on Windows 11 Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 7f69bca41c5034207ba9170420f6b3b214121a7b CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: en-US (en_FI); UI: en-US Calc: threaded
For what it's worth, not reproduced either on Linux: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded nor on macOS: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 2; OS: Mac OS X 13.2.1; UI render: Skia/Raster; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Tooltips pop up, word completion works. HK, can you try still pressing enter on part of a word that you _know_ has already been collected and should be possible to autocomplete? I'm wondering if the issue is just the tooltip not showing. Also, please update to 7.6.2, quite a few bugs have been fixed since 7.6.0 (including a security issue). And if you can still reproduce the issue, please paste here the full version information from Help > About LibreOffice. Thank you!
Hello Stéphane In the meantime we detected, that Word Completion is well functioning if Windows 11 is cleanly installed. So i have a problem with my Win11 Image, that we distributes by our clients. Some software component or configuration is blocking a correct working, but seem's not a general compatiblity issue related Win11 and Libreoffice. We can close the thread, because the problem I have to solve is on my image. Many Thanks
(In reply to HK from comment #10) > In the meantime we detected, that Word Completion is well functioning if > Windows 11 is cleanly installed. > So i have a problem with my Win11 Image, that we distributes by our clients. I believe that this is not correct. Your problem is definitely a duplicate of bug 158139; it is debugged, the cause is identified, and fixed. The analysis have shown that the problem was a changed Windows-specific function, that started to take more window messages into account. That means, that *in some cases* (there there is no messages from the extended list in the queue), the function will continue working; but that is not stable, and a bit changed situation (like heavier system load, or faster typing, or infinite other factors) can easily break it. Anyway, either WORKSFORME or FIXED (bug 158139), this should be OK now.
*** This bug has been marked as a duplicate of bug 158139 ***