Bug 120971 - Bug in LO comment box, the pointer to the cell in reference relocates itself.
Summary: Bug in LO comment box, the pointer to the cell in reference relocates itself.
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.4.5.1 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-27 15:34 UTC by George
Modified: 2019-06-08 02:57 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 George 2018-10-27 15:34:02 UTC
The pointer from the comment box that points to the cell location it refers to will point to the upper left corner of cell "A1" when I move the comment box to a different location, to get it out of the way so I can see the cell blocks it was over.
 When I'm actively working on a cell, I have the comment box open "show comment", so I can see what that clock I'm working on was doing during that segment of that day.
 If I accidentally first move it down, the pointer will then move to A1. If I start out moving in a direction other than straight down, it does fine. This can/will happen any time I first click on the displayed comment box to try to move the box.
 It only happens when I attempt to move it straight down but only if I do that when I first begin to move it. If I move it any direction other than down, it will do just fine. Then I can move it down until I release the left mouse button and press it again to move the box. As long at the first move when I click on the box is NOT straight down. After that, I can move it any direction as long as I have it captured with the left mouse button.
 I'm explaining this the best I can as I am just an average user and NOT a software technical person.
 So far, the bugs I've reported with this comment box have not been resolved for whatever reason. My most recent was NOT found by the LO group and will probably be unresolved like the other bugs I've found.
 So, I'll just keep on reporting these bugs as I get time. There are several more remaining(all dealing with the comment box). The rest of LO seems to be fine.
Comment 1 Telesto 2018-10-27 20:36:26 UTC
Setting back to unconfirmed, someone else needs to confirm it.
Comment 2 Oliver Brinzing 2018-10-28 08:05:14 UTC
Thank you for reporting the bug. 

Please attach a sample document/screenshots or a screen capture video, as this makes it easier for us to verify the bug.
 
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Comment 3 QA Administrators 2019-05-08 18:27:16 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2019-06-08 02:57:47 UTC
Dear George,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp