https://bugs.documentfoundation.org/show_bug.cgi?id=169915
Bug ID: 169915
Summary: CALC - marking highlight in comment is kept while
typing
Product: LibreOffice
Version: 25.8.3.2 release
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Calc
Assignee: [email protected]
Reporter: [email protected]
SUMMARY
When you type a cell comment and mark something, the marked area stays marked
and when you type something the marking still stays in place overwriting the
text there
STEPS TO REPRODUCE
1. Create a cell comment
2. Mark the text until it 'sticks' to your cursor
3. Type something
The bug is not very easy to reproduce, but after some tries I always got it to
show up. The easiest way to reproduce the bug was:
1. Create a cell comment
2. Mark the text using the mouse and hold the left mouse button down
3. Replace the current text
4. Move the mouse around (The marked text sometimes, but not always sticks to
your cursor)
OBSERVED RESULT
The marked text sticks to your cursor and is not cleared when you type
something. This sometimes also shows up without typing anything and sometimes
with double-clicking a single word.
EXPECTED RESULT
When I type something the selection is cleared and nothing is selected to
prevent overwriting other text
SOFTWARE/OS VERSIONS
LibreOffice:
Version: 25.8.3.2 (X86_64) / LibreOffice Community
Build ID: 8ca8d55c161d602844f5428fa4b58097424e324e
CPU threads: 12; OS: Linux 6.14; UI render: default; VCL: gtk3
Locale: de-AT (de_AT.UTF-8); UI: de-DE
Flatpak
Calc: threaded
OS:
Operating System: KDE neon User Edition
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.0
Kernel Version: 6.14.0-36-generic (64-bit)
Graphics Platform: Wayland
ADDITIONAL INFORMATION
1) This might be a Linux-only bug or a wired interaction with KDE - I'm not
sure, but I'll do some further testing on my Windows machine.
2) The bug was very inconsistent to reproduce for me. Sometimes I was able to
reproduce it instantly five times in a row, sometimes I tried around and tested
different approaches for five minutes without it being caused only to do the
exact same thing a second later and the bug showing up. So "Works for me" could
also be that the bug just didn't show up in the testing time.
- I thought that the bug might be caused when you click+hold+drag beyond the
comment box edge, but this way it was very unreliable to reproduce
- I thought that it might be a (or multiple) leading space char(s) in the
comment but it was also very inconsistent to reproduce.
- The easiest was to as described even though this is kind of like 'asking for
trouble' as not very many people would probably work that way. But it was the
most consistent way for me to reproduce the bug
--
You are receiving this mail because:
You are the assignee for the bug.
