Bug 159136 - When spellcheck is on, Enter key triggers correction in a Calc cell.
Summary: When spellcheck is on, Enter key triggers correction in a Calc cell.
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.3.7.2 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: AutoCorrect-Complete
  Show dependency treegraph
 
Reported: 2024-01-11 16:01 UTC by Andreas
Modified: 2024-08-10 03:14 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 Andreas 2024-01-11 16:01:39 UTC
Description:
This behavior perverts the meaning of the enter key. In my case it led to a Kafka-esque struggle to keep an unusual (but for my purposes correct) spelling in a cell. Granted that space key or punctuation keys can trigger auto correction, the enter key never should. It means, "I am fine with this, enter this please".

This appears to be not a bug in the narrower sense, as Libre Office is arguably doing what devs intended. But the intention is mistaken.

It can be worked around by making the edit of a different word or so in the same cell the last thing one does before hitting enter. But not always is a different word there, and users cannot always monitor for random false corrections every time they type and enter contents.

Steps to Reproduce:
1. Ensure spell check / correction is on
2. Type something that gets corrected, e.g. word with 2 capital letters at the beginning or lowercase word after period and space
3. Hit enter

Actual Results:
Words with double uppercase letters are changed to one uppercase; lowercase letters after period and space are changed to uppercase. Generally: supposed corrections are done upon hitting enter.

Expected Results:
At least (and arguably only) upon hitting enter, no spell correction should be done. Enter places the responsibility for spelling with the user.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.3.7.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 16; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: en-US
Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.4
Calc: threaded
Comment 1 Stéphane Guillou (stragu) 2024-01-11 22:42:08 UTC
(In reply to Andreas from comment #0)
> Expected Results:
> At least (and arguably only) upon hitting enter, no spell correction should
> be done. Enter places the responsibility for spelling with the user.
Many users likely want to have their autocorrection rules applied after pressing enter, there's no reason they might be less likely to want to fix a typo (e.g. double capital) or apply a premeditated rule (e.g. "->" replaced by "→") or have an essential tool like URL recognition apply when pressing Enter.
In your opinion, what would then be the user experience of users wanting those rules to apply every time they enter data into a cell? Press Space, Backspace, Enter?

_Maybe_ one could consider a setting that allows _not_ applying autocorrect on pressing Enter.

Workarounds:
- turn rules off (the ones you never want to apply);
- Ctrl + Z after a rule is applied when you don't want it to.
Are those not sufficient?
Comment 2 QA Administrators 2024-07-10 03:13:44 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2024-08-10 03:14:18 UTC
Dear Andreas,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp