Bug 95305 - Cell comments are not drawn properly when the cell is selected for copying
Summary: Cell comments are not drawn properly when the cell is selected for copying
Status: RESOLVED DUPLICATE of bug 41921
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Calc-Comments
  Show dependency treegraph
Reported: 2015-10-24 19:52 UTC by helplibreoffice
Modified: 2023-06-20 07:05 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description helplibreoffice 2015-10-24 19:52:00 UTC
When a cell is selected for copying (moving dotted line around it), the cell comment is not properly drawn.  Part of the cell comment area is obscured by an invisible overlay.

To reproduce:
1. Create a comment in a cell.
2. Select the row containing the cell.
3. Press ctrl+c
4. Hover over the comment indicator to view the comment.

Expected result:
Comment not obscured.

Actual result:
Part of comment area obscured.
Comment 1 m_a_riosv 2015-10-25 00:20:36 UTC
Hi @helplibreoffice, thanks for reporting.

Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b
Version: (x64) Build ID: 0b48731919433e46e4fda7e5a5ca27c08c28b981-GL

Not in:
LibreOffice 3.3.4 OOO330m19 (Build:401), but here comments works in a different way.

Seems the issue is there since automatic show of the comment hovering the cell was implemented.

Changed the version to the first known with the issue.
Comment 2 helplibreoffice 2015-10-25 19:32:54 UTC
You're welcome.  My pleasure.  Thanks for confirming and performing version testing.
Comment 3 QA Administrators 2016-11-08 11:59:47 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2019-12-03 14:50:11 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2021-12-03 04:41:17 UTC Comment hidden (obsolete)
Comment 6 Buovjaga 2023-06-20 07:05:33 UTC

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