Bug 157828 - Support selection of multiple comments
Summary: Support selection of multiple comments
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Comments
  Show dependency treegraph
 
Reported: 2023-10-19 15:38 UTC by Eyal Rozenberg
Modified: 2025-10-20 03:14 UTC (History)
1 user (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 Eyal Rozenberg 2023-10-19 15:38:50 UTC
At the moment, we cannot select more than a single comment (using the LO UI; I'm not sure what's possible under the hood).

It should be possible to select more than one comment - for formatting, for copying their text, for considering deletion etc.
Comment 1 Eyal Rozenberg 2023-10-19 15:40:00 UTC
The ability to select all comments at once was recently found to be useful/necessary to replace a "direct-format all comments" command (see bug 
157522).
Comment 2 Heiko Tietze 2023-10-20 08:55:38 UTC Comment hidden (no-value)
Comment 3 Eyal Rozenberg 2023-10-20 09:10:44 UTC
Heiko, note that I'm asking for the ability to select "regularly", i.e. with a single-click on some part of the comment bubble, and shift+click and ctrl+click working as one would expect. Are you sure this is all obvious and you don't want to discuss which regions exactly would be considered a selection? Or whether the selection should behave similarly to table cell selection, where a click doesn't select but you have to wrestle with it a bit?
Comment 4 Heiko Tietze 2023-10-20 13:35:54 UTC
(In reply to Eyal Rozenberg from comment #3)
> Are you sure this is all obvious...
Implementation details. Tickets don't become more attractive to developers if a lot of comments ponder over every detail. If something is unclear it's easy to ask.
Comment 5 QA Administrators 2025-10-20 03:14:32 UTC
Dear Eyal Rozenberg,

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