Bug 141693 - SpellCheck leaves cursor at beginning of corrected word
Summary: SpellCheck leaves cursor at beginning of corrected word
Status: RESOLVED DUPLICATE of bug 137972
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All macOS (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-14 16:33 UTC by Dave
Modified: 2023-02-02 14:07 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dave 2021-04-14 16:33:45 UTC
Description:
After using right-click menu to spellcheck/correct a misspelled word, LO leaves the cursor at the beginning of the word, an awkward decision which requires intervention to proceed typing additional words. Many other apps (this text entry box in FireFox) leave the cursor in a more desirable location, at the end of the corrected word, where it is ready to continue with forward progress. 

Even if you don't necessarily see this as a problem, it is likely that you also don't see any benefit to leaving the cursor at the beginning of a word over leaving the cursor at the end of the word. 

Please adjust LO to put the cursor at the end of the word after spell check makes a correction. 

Steps to Reproduce:
1.misspell a word
2.right-click on the word & select the correct spelling
3.notice where the cursor is left... Before the corrected word. 

Actual Results:
Cursor is placed before the corrected word

Expected Results:
Expected to see cursor placed after the spell check corrected word. 


Reproducible: Always


User Profile Reset: Yes



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Mac OS X (All)
OS is 64bit: no
Comment 1 Telesto 2021-04-15 15:13:40 UTC
Same opinion, it's actually a regression. It did work properly in the past. But fix for A, broke B and the developer in question finds it kind of triviality. 

It's surely a detail, but I think it matters. 

Anyhow marking it a duplicate

*** This bug has been marked as a duplicate of bug 137972 ***
Comment 2 Heiko Tietze 2023-02-02 09:34:51 UTC Comment hidden (obsolete)
Comment 3 Telesto 2023-02-02 14:05:43 UTC Comment hidden (obsolete)
Comment 4 Telesto 2023-02-02 14:07:58 UTC Comment hidden (obsolete)