search

ONLYOFFICE / DocumentServer

ONLYOFFICE Docs is a free collaborative online office suite comprising viewers and editors for texts, spreadsheets and presentations, forms and PDF, fully compatible with Office Open XML formats: .docx, .xlsx, .pptx and enabling collaborative editing in real time.
https://www.onlyoffice.com
GNU Affero General Public License v3.0
4.87k stars 1.09k forks source link

Problem writing comments in collaborative document. #826

Open chinicuin opened 4 years ago

chinicuin commented 4 years ago

Do you want to request a feature or report a bug? bug

What is the current behavior? Sometimes when editing a collaborative docx document can't write comments using the left panel.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. I'm using the online onlyoffice version 10.5.2, all the steps have been performed in that platform. Create a docx document. Create a user account named user2 (my account is user1). I opened the document and send invitation to previously created user, given him full permissions. User1 open the left panel --> comments, and start to write the comment in the input text area. At the same time user2 starts writing something in the document. If user1 keeps writing in the text area while user2 is writing on the document, the focus of user1 changes to the document. As a result, user1 starts writing in the document, not the text area as intented. If user1 add a comment via right click --> add comment, everything's fine.

What is the expected behavior? Don't lose focus on the input text area from the comment menu, even if another user is writing at the same time.

Did this work in previous versions of DocumentServer? No. Tested in Presentation editor version 5.0.6 and current version 5.5.0 (Online platform version 10.5.2)

DocumentServer version: Current version 10.5.2 (online)

Operating System: Mac OSX Mojave 10.14.6

Browser version: Chrome 80.0.3987.132 (Build oficial) (64 bits)

Rita-Bubnova commented 4 years ago

Hello, @chinicuin. Thank you. I can confirm - this is a bug, issue 44918 in our internal issue tracker.