EDITING Auto input is enabled. The column contains identical rows in cells. When editing existing text, auto-input is triggered. This prevents you from making the desired changes. https://forumooo.ru/index.php?topic=10864.0
Hi Frants Can you please: - provide precise steps to reproduce the issue - and attach a file if that helps - share with the us the version information copied from Help > About LibreOffice Is the issue related to the autocomplete of a cell value, based on the existing values in the same column? Thank you!
Created attachment 190097 [details] Example Version: 7.6.1.2 (X86_64) / LibreOffice Community Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: CL threaded
[Automated Action] NeedInfo-To-Unconfirmed
Reproduced in: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9a02f4ed071f15908624fb1cafcf6dbb72b00a1b CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Trying to change a lowercase c to an uppercase C in the word "Cont." and then pressing Enter will autoinput to the existing value above the cell - but that's because Tools > AutoInput is on. (Noting that this might look like a regression to some since at fileopen, this only started in 7.4 with the fix for bug 144308. But if the column is edited first, the same thing happens before that fix, and since OOo 3.3 times.) This can be worked around with: - a Ctrl + Z to undo the autoinput. - or turning off autoinput entirely The main issue here is that it is not obvious the value will be "autoinputted" because there is no hint. Usually, the extra characters are highlighted in "negative", but in this case nothing shows it will change. So I've changed the summary, I hope that makes sense? Mike and Heiko, what do you think would be a good way to indicate that the value will change on pressing Enter? Highlight only the character that will be replaced? Would be consistent, in my opinion.
(In reply to Stéphane Guillou (stragu) from comment #4) > The main issue here is that it is not obvious the value will be > "autoinputted" because there is no hint. "there is no hint" is the whole issue here, then is a bug, and that must be fixed.
I regret that I do not have MSO available, I would check how MS Excel does this. But still, this behavior of LO is wrong, in my opinion. If I explicitly correct the text, despite the autoinput hint, then the autoinput option will be accepted, not the user's. How can I insist on my version? Disable auto-input? But it is useful to me in other cases. Who will turn on and off auto-input in every “inconvenient” case? I believe that if the user began to make a correction to the text other than the one suggested by autoinput, then the user's variant should be accepted. And also, I want to note that when I edit the text, the extra characters are highlighted with an inverse background.
Created attachment 190105 [details] Video, demo When I edit text, extra characters are highlighted with an inverse background.
Just tested with Office 365 and indeed, even though autoinput is on, going back to a value and changing the capitalisation does not trigger autoinput. Example in Office 365: 1. Insert in A1: some words <Enter> 2. Insert in A2: some W <Enter> Result: it autocompletes with "some words" (lowercase version), which makes sense to keep data consistent. However, if editing A2: A) mid-string change in capitalisation: no autoinput suggestion, accepts edit (different to LO) B) remove character(s) at the end of the string: no autoinput suggestion, accepts edit (same as LO) C) remove characters at the end of the string, then add characters that match a previous value: autoinput active (same as LO) If several values match, a list is shown, without a default selection. (Different to LO.) I tend to agree with Frants now, in that this MS Office behaviour for case A should be preferred, and an existing value should not be forced on the user if they are going back to change the case of some characters mid-string.
Created attachment 190108 [details] Video, demo, Google sheets I agree with Stéphane Guillou. I tested these texts in Google Sheets. You can edit your version and apply it successfully (unlike LO)!
Created attachment 190276 [details] Auto-complete with MS Excel * Do not auto-complete on deletion. * Do not auto-complete on editing within the word. * Do not correct different upper case. * Offer auto-completion based on case insensitive pattern (and do not change the case). First two are implemented but case-insensitivity not.