Description: As in summary. Cursor sometimes can be seen misplaced (not always reproducible). Steps to Reproduce: 1. Open a Writer document. 2. Open a new window for the same document. 3. Change zoom level in the active window. Actual Results: Actual window zoom level changes. Other window horizontal position changes. Expected Results: Actual window zoom level changes. Other window horizontal position remains the same. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.7.2 (x64) / LibreOffice Community Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: es-MX (es_ES); UI: en-US Calc: CL
After a bit more test: - Zoom level for the active window must be not much greater than the page width. - The horizontal ruler becomes misaligned (usually in the non-active window, sometimes in both windows). Version: 7.3.3.1 / LibreOffice Community Build ID: 30(Build:1) CPU threads: 1; OS: Linux 5.14; UI render: default; VCL: gtk3 Locale: es-MX (es_ES.UTF-8); UI: en-US Calc: threaded
I don't see the cursor position error. What I get instead is that the page is positioned in a different spot. When I click the document it is centered. Alternating between the original window and the new window cause this repositioning of the page. Seems like a bug to me. But probably it manifests differently in windows? I'm on Linux / kf5.
oops sorry i have edited the wrong bug. Please verify version and HardWare
Confirm Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 9063d99ff5ee43cc1239fc1dbb5d9897bdda1c9b CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded also in Version: 6.0.0.0.alpha0+ Build ID: 9127d1a89cbfba89eb9df6755ea7b9e161cfc67a CPU threads: 4; OS: Windows 6.3; UI render: default; Locale: nl-NL (nl_NL); Calc: CL Far less common, but still happening with Versie: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 Locale: nl_NL
*** This bug has been marked as a duplicate of bug 43253 ***