Bug 80035 - Other: Comment block base point option not working
Summary: Other: Comment block base point option not working
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.3.0.0.beta2
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks: Calc-Comments
  Show dependency treegraph
 
Reported: 2014-06-14 20:27 UTC by Andrey Kozhevnikov
Modified: 2023-12-04 03:16 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 Andrey Kozhevnikov 2014-06-14 20:27:45 UTC
Problem description: Comment block have options for changing base point position under position and size menu, but it's not working and not even saved

Steps to reproduce:
1. Create comment for any cell
2. From context menu of comment block change base point position

Current behavior: base point not changing

Expected behavior: base point should be changed and arrow destination should be relocated

              
Operating System: Ubuntu
Version: 4.3.0.0.beta2
Comment 1 Jorendc 2014-06-14 20:29:47 UTC
Repro, 4.3b2.

Kind regards,
Joren
Comment 2 QA Administrators 2015-07-18 17:44:10 UTC Comment hidden (obsolete)
Comment 3 Buovjaga 2015-10-23 08:24:50 UTC
Still repro.
Show comment - right-click, position & size.

Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+
Build ID: fcc2415ade6ae93710bbbda9f7e163045e323105
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-10-21_16:55:13
Locale: fi-FI (fi_FI)
Comment 4 QA Administrators 2016-11-08 11:19:22 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2019-12-03 14:16:27 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2021-12-03 04:31:16 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2023-12-04 03:16:18 UTC
Dear Andrey Kozhevnikov,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug