Description: When using LibreOffice Calc under Wayland dragging a column is very difficult, if you need to move the column beyond the window border. When you select a column, hold ALT and start dragging, the column moves normally withing the window. However if you hold the cursor near the left or right border of the window nothing happens until after a few seconds. After a few seconds the view jumps directly to the "end" of the sheet. If you try the same thing under X and hold the cursor near the border of the window, the columns scroll sideways and you are able to see where you're about to place the column. The issue it not present under XWayland - forcing LibreOffice to run in XWayland with an Environment Variable is the only workaround i found so far when in a Wayland session. Steps to Reproduce: 1. Select a column in any open spreadsheet 2. Hold the ALT key and drag the column to move it to the right 3. Try moving the column beyond the window border Actual Results: When you hold the cursor at the window border, while dragging the column, the view does not move smoothly, but jumps suddenly to a column far to the right. Expected Results: Instead the columns should start scrolling to the right once you try to drag a column to the right beyond the window border, allowing you to see where in the sheet are you placing the column. Reproducible: Always User Profile Reset: No Additional Info: I have not tried resetting the user profile, but i tried reinstalling, i have also tried it under different distributions and different DEs. It's present in all that i tried (OpenSuse Tumbleweed KDE; KDE NEON User Edition). It's also reproducible with the Flatpak version (tried that one at the time i'm posting this - LibreOffice version 7.5.2.2). Below is the About LibreOffice information from the system i use normally (OpenSuse TW with KDE): Version: 7.5.2.1 (X86_64) / LibreOffice Community Build ID: 50(Build:1) CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
I can see that dragging a cell selection to the right edge often results in large jumps. Tested in: Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded as well as with kf5 (cairo+wayland). Any chance you could share a video of the behaviour, to make sure we see the same thing? Note that with kf5, there is an issue in shifted drag-and-drop target that is resolved with commit f51b220b953ec71fb742f799fbe645a93cf3d944. Could be good to test with a recent master build: https://dev-builds.libreoffice.org/daily/master/current.html
Created attachment 186576 [details] Screen recording of the bug
(In reply to maan from comment #2) > Created attachment 186576 [details] > Screen recording of the bug Hi Stéphane, i just created this recording. The version is: Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded I have not tested with the master build, as I am working from this machine and I use LibreOffice constantly. I don't really want to reinstall and reconfigure it. Maybe I can try it in a virtual machine when i have time, if that would help?
(In reply to maan from comment #3) > (In reply to maan from comment #2) > > Created attachment 186576 [details] > > Screen recording of the bug > > Hi Stéphane, i just created this recording. The version is: > Version: 7.5.2.2 (X86_64) / LibreOffice Community > Build ID: 50(Build:2) > CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+wayland) > Locale: en-US (en_US.UTF-8); UI: en-US > Calc: threaded > > I have not tested with the master build, as I am working from this machine > and I use LibreOffice constantly. I don't really want to reinstall and > reconfigure it. Maybe I can try it in a virtual machine when i have time, if > that would help? Actually, i just managed to test the master build mentioned. The issue is still there for me.