Bug 138768 - EDITING Undo auto-capitalization after tab inserts both capitalized and uncapitalized
Summary: EDITING Undo auto-capitalization after tab inserts both capitalized and uncap...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.1.5.2 release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: AutoCorrect-Complete
  Show dependency treegraph
 
Reported: 2020-12-09 10:37 UTC by Felix W. Dekker
Modified: 2020-12-25 21:36 UTC (History)
2 users (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 Felix W. Dekker 2020-12-09 10:37:50 UTC
Description:
Impress automatically capitalizes the first character of a sentence after pressing the Tab button. Undoing this by pressing Ctrl+Z causes weird behaviour: After the first undo the tab is removed (good), but after the second undo the lowercase character is inserted in front of the uppercase one (bad). Only after the third undo is the uppercase character removed.

Steps to Reproduce:
1. Create a new presentation.
2. Select a text input in one of the slides.
3. Write "sentence" (lowercase) and then press Tab. You now have "Sentence ".
4. Undo (Ctrl+Z) to remove the Tab character. You now have "Sentence".
5. Undo (Ctrl+Z) to undo the auto-capitalization.

Actual Results:
The second undo changes "Sentence" to "sSentence".

(After an (optional) third undo you have "sentence".)

Expected Results:
The second undo should change "Sentence" to "sentence". The third undo should not be necessary.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
The issue does not occur when pressing Space or Enter instead of Tab.

The issue does not occur in Writer.
Comment 1 Felix W. Dekker 2020-12-10 21:15:16 UTC
I can reproduce this issue on Windows 10 x86-64, Impress 7.0.3.1.
Comment 2 pavlog 2020-12-25 21:36:03 UTC
Thank you for reporting the bug. I can confirm that the bug is present in

Version: 7.2.0.0.alpha0+ (x64)
Build ID: ecb916667b633f8647790e040226b093760e6cfe
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL