Screen jumping, when multi user is editing - image_
Opened this issue · 3 comments
This issue is unique.
- I have used the search tool and did not find an issue describing my bug.
Operating System of DocumentServer
Docker
Version information
v8.2.2
Expected Behavior
Not have screen jumps during the cases which are described in the actual behavior.
Actual Behavior
Hello team
we found some screen jumping scenarios during our usage of onlyoffice 8.2
First scenario is happening when there are media (images) and tables
Whenever USER 1 cursor stands within the table (and within one page view, not within multi page view) and USER 2 makes changes on top (or may be in any place), USER 1's screen jumps (approximately 1-2 page up)
Please find attached video with images
Second scenario , when there are page breaks - jumping effect only happens when we encounter a page breaker, when some content needs to move from one page to the following one (regarding of where in the doc).
Please find attached video as well
Possible root causes might be different cases , than it is described, but at least, with this steps you can reproduce issues.
Attaching documents as well , that you can have the same test scenarios
Reproduction Steps
No response
Additional information
test screen jump - breakdown.docx
screen.jumping.-.page.breakers.mp4
screen.jumping.-.with.image.mp4
@ElenaMaaya any kind of updates/estimations/status changes related to this issue ?
Were you able to reproduce the issue ?
Thanks
Hello @amovsisyan .
Thank you for your attention to our product!
I think these are two different issues.
I can confirm that the issue in "test screen jump - images.docx" exists.
I have created bug 72234 for this issue.
Unfortunately, I can't reproduce the problem from "test screen jump - breakdown.docx" on Windows 11 DS v.8.2.2.
Please create a new issue for problem in file "test screen jump - breakdown.docx".
And please, press the "Nonprinting characters" option in the Home tab in the test file and shoot a video again. Please put this video in a new issue.
Thank you for your understanding and help! We try to follow rules one issue - one bug.
As it was torturing me so much, I looked into the code and tried to manage some fixes.
As you guys know a lot more than me from code, can you pls double check the fix on your side and make sure that?
- this fixes the current problem
- does not make any other problems
Here is a PR from my fork
tagging: @Rita-Bubnova @ElenaMaaya
Thanks