Bug 106152 - moving view cursor over a comment anchor position is faulty
Summary: moving view cursor over a comment anchor position is faulty
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Writer-Comments
  Show dependency treegraph
Reported: 2017-02-23 10:16 UTC by Pranav Kant
Modified: 2023-03-08 03:26 UTC (History)
3 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 Pranav Kant 2017-02-23 10:16:33 UTC
Open a plain odt, write a sentence, insert a comment, reply to these comments (so to have a comment thread).

Now move the cursor through left/right arrow keys over the anchor position. You require multiple left/right arrow key hits (which is equal to the length of comment thread at that anchor position).

Don't think this should be the expected behavior here. User probably expects only one left/right arrow key moving over the anchor position.

Moreover, this leaves scope of breaking the comment thread when user presses some key when the cursor is in one of the intermediate states/positions around the anchor position.
Comment 1 Aron Budea 2017-03-03 21:42:02 UTC
This stems from the way the comment anchoring is implemented, via inserting a special element in the text (or something like that).

Confirmed in and 3.3.0 / Windows 7.
Comment 2 QA Administrators 2018-03-05 03:38:36 UTC Comment hidden (obsolete)
Comment 3 Pranav Kant 2018-03-06 05:13:02 UTC
Still reproducible: Version:
Comment 4 QA Administrators 2019-03-07 03:43:43 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2021-03-07 04:14:56 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2023-03-08 03:26:10 UTC
Dear Pranav Kant,

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