When you tap Ctrl+C and then move to another cell and press Return (to edit it), Return (surpringly - to some) works as Ctrl+V / paste.
Normally when you paste into a cell (using Ctrl+V or a custom shortcut) that overwritten cell gets highlighted - but when LibreOffice pastes using Return (in its special Return-works-as-Ctrl+V mode) the cell doesn't get highlighted.
Created attachment 44242 [details]
Visualization of the issue - return doesn't highlight.
Another dark theme again!!!
BTW, when you paste by ENTER, you don't do Ctrl-V beforehand; it's Ctrl-C and ENTER. No Ctrl-V in the middle. Can you try that instead?
Meanwhile, when there is a pre-selection, doing paste by ENTER should not have cleared the selection. That part is a bug.
(In reply to comment #3)
> BTW, when you paste by ENTER, you don't do Ctrl-V beforehand; it's Ctrl-C and
> ENTER. No Ctrl-V in the middle. Can you try that instead?
Yes - I only press Ctrl+C - arrow down a few times - then Return (not Enter on the NumPad).
Ah yes - I didn't notice the the hightlight of the copy buffer source disappeared. That's not serious - it's just cool when the highlight is there :)
(In reply to comment #5)
> (In reply to comment #3)
> > BTW, when you paste by ENTER, you don't do Ctrl-V beforehand; it's Ctrl-C and
> > ENTER. No Ctrl-V in the middle. Can you try that instead?
> Yes - I only press Ctrl+C - arrow down a few times - then Return (not Enter on
> the NumPad).
Ah, then I can't reproduce it on my end I'm afraid.
Ah, I got it. When you copy and paste-by-enter (or return) only a single cell, Calc won't highlight the pasted cell. When you copy and paste-by-enter a cell range i.e. more than one cell, then it highlights when pasted.
I can have this fixed on a single-cell-paste case.
I now remember the rationale. The selection was cleared to allow the cursor to move downward on subsequent return/enter. So, this behavior of not highlighting a single selection was in fact intentional.
However, after thinking about this a bit, I'm in favor of removing this behavior, for now. In the future we plan to change the cursor behavior itself, so this behavior might change again. But that's a long term plan.
Fixed on master.