Created attachment 185042 [details] Recording of partial Writer Window (right part truncated for privacy and for size reasons) Situation: I had opened a document, enabled "track changes" and displayed a specific part of a document in a window. As I wanted to write a similar part to the same document I opened a second window to view the first part and started typing on the original window... What happened: Every key press caused significant flickering (actually it seemed the whole content was shifted horizontally by a significant amount momentarily). Also the cursor was offset several centimeters to the right where the text had been entered actually. However when clicking to empty space, the cursor was re-positioned to the actual end of the text. See the video recording... This seems to be "yet another oddity when using multiple views on a document", and it seems something is fundamentally broken or "mis-implemented" with multiple views (windows) of a document.
Please test with a clean profile, Menu/Help/Restart in Safe Mode
The point is I cannot reproduce the effect at will: When I opened the same document and did about the same thing, Writer reacts normally. Instead I had another oddity while trying to reproduce: When I click a heading in the navigator, the cursor jumps to the corresponding entry in the table of contents for one windows, while for the other window the cursor jumps to the correct heading. I also managed to swap the roles between both windows. Eventually both windows behaved correctly.
(In reply to Ulrich Windl from comment #0) > Situation: > I had opened a document, enabled "track changes" and displayed a specific > part of a document in a window. As I wanted to write a similar part to the > same document I opened a second window to view the first part and started > typing on the original window... Tried to repro, no jumping here. Please copy and paste here the contents of your Help - About (LibreOffice - About on macOS) by clicking the copy button. This allows us to know more about your system. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b5c3a7502f7ff6ccf0f829c1f3a2ba50b8584c41 CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_FI); UI: en-US Calc: threaded
Dear Ulrich Windl, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Ulrich Windl, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp