Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug with adding comments on text over page boundaries #287

Closed
pi-xel opened this issue Apr 25, 2018 · 4 comments
Closed

Bug with adding comments on text over page boundaries #287

pi-xel opened this issue Apr 25, 2018 · 4 comments

Comments

@pi-xel
Copy link

@pi-xel pi-xel commented Apr 25, 2018

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

bug

What is the current behavior?

When adding a comment on some text snippet by selecting the snipped, right-click, add comment and if the text snippet goes over a page boundary (i.e. over two different pages), the text marked alongside the comment is not only the previously selected, but everything until the end of the document is marked.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

See above.

What is the expected behavior?

After adding the comment, only the previously selected text is marked alongside the comment.

Did this work in previous versions of DocumentServer?

Don't know, it occurs on a fresh install of the DocumentServer.

DocumentServer version:

5.1.2 CE (from current docker image)

Operating System:

Ubuntu 16.04.4 LTS, 64 bit, kernel version 4.4.0-119-generic, docker version 17.05.0-ce

Browser version:

Google Chrome 66.0.3359.117, 64 bit

@pi-xel
Copy link
Author

@pi-xel pi-xel commented Apr 25, 2018

Note: the bug seems to appear only in the graphical representation of the document, if I download the doc later via nextcloud and open it in libreoffice writer the comment correctly relates to the previously selected text snipped.

@ShockwaveNN
Copy link
Member

@ShockwaveNN ShockwaveNN commented Apr 25, 2018

@pi-xel Hi there, this is already a known bug (#37425 in private bug tracker) - this will be fixed in 5.1.3

@pi-xel
Copy link
Author

@pi-xel pi-xel commented Apr 25, 2018

@ShockwaveNN Thanks for the info & quick reply.

@ShockwaveNN
Copy link
Member

@ShockwaveNN ShockwaveNN commented May 4, 2018

Issue should be resolved in 5.1.3

@ShockwaveNN ShockwaveNN closed this May 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants