Thanks for filing this issue Claudio.
Looks as an interesting improvement to me > New enhancement. 
Ciao - Cor

Yeah, as judging by your screenshot, this appears to be a problem for high-DPI screens.

Created attachment 122236 [details]
File open directly with LO

Hi,

Thank you for your responses. I'm not sure whether it is a question of high-DPI screen. Please find attached two screenshots at the same "zoom":

(1) the document is open directly with LO: width of comments is too narrow.
(2) the document is open with LO through Wine: here the width of comments is OK.

To be sure it would help to be able to widen the comments as an improvement ; but it seems to me that the two very different widths (and the fact that the comments with a narrow width are barely readable) pleads for considering this as a bug (?). Or is it that the version 4.4.7.2 has a different default width of comments? (I know I should've tested with the same version but... I took the most recent one on the web for other purpose.)

Thank you.

Claudio

Version witb narrow comments:
Version: 4.4.3.2
Build ID: 40m0(Build:2)
Locale: en_GB

Version with large comments (through Wine 1.7.55):
Version: 4.4.7.2
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale: en_GB

Created attachment 122237 [details]
File open through Wine

I can confirm this is still the case with 5.1.1.3

also https://bugs.documentfoundation.org/show_bug.cgi?id=73953 is related but older.

This should be merged with bug 73953 and probably bug 95958

I absolutely support this issue. I’m working on a Dokument with several people and the number of comments led to very small comment boxes. Up to the point where I can read only the first two lines of a comment of quite long texts.

Actually, when you use the navigator and hover (mouser over) a comment, a pop up shows the entire comment. A function like that would work for me as well, when hovering over the normal comments.

Of course simply adjusting the width of the column seems to be the easiest solution.

This is also an example that the developer community ignores important user requests for years. It was already requested in 2013.

In collaborative work it is definitely necessary to be able to adjust the width of the comment column in LibreOffice Writer.

Sometimes I suspect that there are some influential people, who want to keep LibreOffice away from professional use. 

Here is another example for my suspicion:
Bug 54393, which I reported in 2012, is still present. So nobody, who wants to write Articles with the Vancouver system for citing, can use LibreOffice.

Working with document with lots of comments in LO 6.4 is still a big issue. It's hardly possible to follow. The visible part of a comment is tiny (you have to scroll within the comment which makes it hard to follow); comments are not aligned with the text, etc.. 
I had to open the doc with LO online to be able to work (which handles the display of comments a bit better, though also has issues). As much as I resent Google, LO could do with getting a little inspiration from Google Docs hen it comes to usability.

Adjusting the width of the comment column/pane seems like good approach to address issues with the display of comments.

I'd say that this feature is very important! And overall the comment function is outdated (and looks outdated too). Since collaboration on docs has become very normal, I thin it should be a priority for LLO to address the redesign of it. A couple of things for e.g.

 - Resizing the width of the column (this bug)
 - Making it easier and more dynamic to select comments in a doc so it's more aligned with where the comment relates to in the text (with lots of comments it's currently difficult sometimes to find / select the comment)
Inspiration from google docs (and hell I do not support Gdocs) on the UI for comments wouldn't be a bad thing I think

I would also really appreciate if this feature was implemented - LO Writer is really nearly a perfect drop-in replacement for MS Office on Linux, but working with documents with many comments is extremely painful because of this inflexibility in terms of their width.

FYI to the other people encountering this issue, I discovered today that using the "Navigator" (press F5) is one way to make this process slightly less painful since it shows all the comments and at least on my system (Ubuntu 20.04 w/ KDE Plasma desktop), you can "mouse over" and see the full comment - so you don't have to scroll through the tiny comment box. Also, double-clicking the comment in the Navigator brings you to the place in the document where the comment was made. 

This does require you to have two windows open side by side (the document and the navigator) so isn't really feasible except with an external monitor. And you also have to keep the comment boxes open at the same time so obviously the fix requested here would be much better and less redundant.

I work in an international organisation that uses comments in documents intensively for their internal discussions. We have many lengthy comments with lengthy replies to them. Allowing for a wider column would be a good step to make LibreOffice more useful for us.

(In reply to Robert from comment #20)
> I work in an international organisation that uses comments in documents
> intensively for their internal discussions. We have many lengthy comments
> with lengthy replies to them. Allowing for a wider column would be a good
> step to make LibreOffice more useful for us.
Thanks Robert. Good that you explain the importance. Also, I guess you do know how it works in open source.. ;)  So if you find options to speed this up, it may also help you(r organization).

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

*** Bug 149054 has been marked as a duplicate of this bug. ***

We should not just enlarge the comments columns but introduce a splitter that allows resizing.

(In reply to Heiko Tietze from comment #42)
> We should not just enlarge the comments columns but introduce a splitter
> that allows resizing.

+1 to this idea

*** Bug 149405 has been marked as a duplicate of this bug. ***

Still a problem ... :(

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