Bug 154691 - Cycle Case command doesn't work during cell edit
Summary: Cycle Case command doesn't work during cell edit
Status: RESOLVED DUPLICATE of bug 105977
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.5.1.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-06 19:13 UTC by Eyal Rozenberg
Modified: 2023-04-08 09:33 UTC (History)
1 user (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 Eyal Rozenberg 2023-04-06 19:13:33 UTC
Suppose I've added the "Cycle Case" command to the Cell Edit context menu in Calc. Now, in a new document, I enter some text into a cell, and in edit mode, select one of the characters, right click, and select Cycle Case repeatedly.

I see different behaviors, most of them wrong:

* Case cycled for entire cell contents, edit mode exited
* Nothing happens on repeated Cycle-Case commands
* The selected character is deleted

I think the cycling of the whole cell contents is characteristic of selecting the last character.

Anyway, it doesn't consistently behave like I expected too.
Comment 1 ady 2023-04-06 20:20:31 UTC
Even if you select specific characters within a cell, the Cycle Case command seems to apply to the whole cell, not to the specific selected text.

Other Casing formats (e.g. UPPERCASE) can be applied to the selected text, and the characters are still selected/highlighted after the command was applied, so additional commands/attributes can be applied to the same selection.

In contrast, selecting specific characters within a cell, the Cycle Case command will act on the whole cell and previously-selected text will not be selected (highlighted) anymore.

I have not tested what exactly happens with the Casing of the whole cell according to several possible initial combinations of upper and lower case characters, because currently it doesn't apply to the situation presented in comment 0.
Comment 2 Stéphane Guillou (stragu) 2023-04-08 09:33:17 UTC
let's add to the existing bug 105977

*** This bug has been marked as a duplicate of bug 105977 ***