Description: Auto-capitalize activated when pressing CTRL+ENTER in a merged cell for splitting text manually Steps to Reproduce: 1. Open the attached file 2. Enter the cell in C9 3. Put cursor before "going" 4. Press CTRL+Enter 5. Exit the cell by pressing enter or clicking somewhere else Actual Results: uppercase for going Expected Results: No uppercase change at all or instantaneous not after leaving the cell Inspired by: bug 145921 Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: ddc57169ac8d1de00403dbb09fef5221beaa0f3d CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL also in 4.4.7.2
Created attachment 176552 [details] Example file
The sudden auto-capitalize after cell exit is bothering me the most.. but well not a heavy Calc user myself at this being there since a long time..
The simple solution to your concerns is to uncheck the "Capitalize first letter of every sentence" option under Tools -> Autocorrect -> Options. My take: NAB
(In reply to Dave Barton from comment #3) > The simple solution to your concerns is to uncheck the "Capitalize first > letter of every sentence" option under Tools -> Autocorrect -> Options. > My take: NAB Well this doesn't happen when putting the same sentence in Writer & pressing Enter before 'going' which makes it behave differently anyhow. (with Capitalize first letter of every sentence) enabled And there are two aspects a) Should it Capitalize b) when should it be applied (while typing or only after exit of the cell)
What has anything in Writer to do with a "claimed" bug in Calc? They are two separate components of the software, with different Autocorrect settings. If there is a provable bug in Writer then file a separate report. In answer to a): Yes,if a user sets an option the software must ALWAYS respect the user's selection. In response to b): How is this relevant or of any importance?
(In reply to Dave Barton from comment #5) How is this relevant or of any importance? a): Yes, if a user sets an option the software must ALWAYS respect the user's selection. True. However even within the option enabled there are apparently differences of interpretation how it should work in subsets of cases. The same option functioning differently across components does reduce the predictability. There might be valid reasons doing so. I simply don't know. b) when should it be applied (while typing or only after exit of the cell) Has to do with user feedback & undo Heiko argued (IIRC) - Markdown - that enabling by default is 'functional' and could be overruled by a single CTRL+Z. Same applies to "Capitalize first letter of every sentence" In the case here even undo doesn't function. In my perception "Capitalize first letter of every sentence" A) shouldn't kick in at all in the specific case (comparing with Writer) B) Or subsidiary: should Capitalize, but instantaneously after CTRL+ENTER (with undo option) C) Even more subsidiary: some undo capitalize should be available after exit. D) It's all perfectly well design already I don't know with to exactly expect. The current situation doesn't seem 'ideal' to me; based on bug 145921 and my own testing. That's why I'm throwing this at UX. It's more an observation; without a clear how it should be answer. I can't tell. That's why I'm putting this forward.
As step 5, add a space after "going", and also you will get "Going". If do you want to avoid the AutoCorrect Option, exit the cell while the cursor is in other word, not in "going". I think that this is the expected behaviour. But I am not sure if Ctrl+Z must undo the capitalization. LibreOffice 7.1.7.2.
If you want to capitalize the first word but not the one after a soft break you have to enter space to get the uppercase while editing, which allows you to undo this, and now you can exit the cell keeping it lower case. IMO we must not change any content on exit. It's okay during the operation but not if you finish the operation. And I don't see a reason why this would have been implemented intentionally.
Duplicates bug 98913
Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug