Bug 92176 - Caseless letters trigger "Correct accidental use of cAPS LOCK key"
Summary: Caseless letters trigger "Correct accidental use of cAPS LOCK key"
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: Other All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: AutoCorrect-Complete
  Show dependency treegraph
Reported: 2015-06-19 07:10 UTC by HD
Modified: 2021-01-29 15:07 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description HD 2015-06-19 07:10:05 UTC
When a language inputs a mixed letter and pushes the [Enter] key, the following problems happen.
・ The capital letter of the alphabet becomes the small letter
・ [Caps Lock] becomes invalid

Steps to reproduce:
1:click New spreadsheet menus[Tools] → [AutoCorrect Options].
2:open the DIALOG "AutoCorrect "→ [Options] tab.
3:add a check to "Correct accidental use of cAPS LOCK key".
4:click [OK].
5:push [Shift]+[Caps Lock] and validate [Caps Lock].
6:input with "あA" in Cell.

Expected behavior:
・Please View with "あA".
・Please maintain [Caps Lock].

Current behavior:
・It View "あa".
・[Caps Lock] becomes invalid

In the case of Japanese "Correct accidental use of cAPS LOCK key"
Please invalidate it.

Version :4.2.7
Operating System:Windows7
Comment 1 tommy27 2015-06-19 08:33:35 UTC
you are using an obsolete LibO version (4.2.7)

you should upgrade to 4.3.7 or 4.4.3 and retest
Comment 2 Urmas 2015-06-20 13:06:18 UTC
Confirmed in 5.1 alpha.

HD: Please write any further bug reports in proper English.
Comment 3 QA Administrators 2016-09-20 10:12:05 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2019-12-03 14:41:05 UTC
Dear HD,

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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team