Download it now!
Bug 87910 - accidental usage of capslock is not working
Summary: accidental usage of capslock is not working
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.3.5.2 release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-31 14:33 UTC by sarojinip
Modified: 2015-09-04 03:02 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
screen shot of error reported (182.05 KB, image/jpeg)
2014-12-31 14:33 UTC, sarojinip
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sarojinip 2014-12-31 14:33:28 UTC
Created attachment 111577 [details]
screen shot of error reported

accidental usage of capslock key while typing a paragraph is not auto corrected and error intimation is not shown in the presentation
Comment 1 sophie 2014-12-31 15:03:30 UTC
Hi, it's not auto corrected but it is underlined if the spellcheck for the language is installed and correctly set. Did you check that the language and spellcheck are correctly set? Sophie
Comment 2 Robinson Tryon (qubit) 2015-01-02 21:33:29 UTC
Comment on attachment 111577 [details]
screen shot of error reported

fix mimetype
Comment 3 Robinson Tryon (qubit) 2015-01-02 21:41:24 UTC
TESTING with LO 4.4.0.1 + Ubuntu 14.04

(In reply to sarojinip from comment #0)
> Created attachment 111577 [details]
> screen shot of error reported
> 
> accidental usage of capslock key while typing a paragraph is not auto
> corrected and 

REPRO Steps:
1) Open Impress
2) Type a sentence

"The quick brown fox jumped over the LASER"

3) Hit the CAPSLOCK key
4) Continue typing a sentence with lower and UPPER case words"

"wALRUS HATS FOR eVERYONE"

RESULT:
When I hit the spacebar at the end of the "wALRUS", the word changed to "Walrus", and CAPSLOCK was disabled by the program.

So NOREPRO from me: The 'accidental' use of CAPSLOCK was corrected.

> error intimation is not shown in the presentation

I don't know what that means.

Status -> NEEDINFO

(please change back to UNCONFIRMED after you explain what 'error intimation' is)
Comment 4 QA Administrators 2015-07-18 17:36:49 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


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


Warm Regards,
QA Team

This NEEDINFO message was generated on: 2015-07-18
Comment 5 QA Administrators 2015-09-04 03:02:03 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO
Message generated on: 2015-09-03