1. Open a sheet with several conditional formatting rules. 2. Go to Format -> Conditional -> Manage 3. Edit a rule. Notice the position of the "Conditional formatting for..." range. 4. Click the mouse in the range box to make the position more obvious in the next step. 5. Press Enter to close the dialog. 6. Edit another rule. 7. Notice how the mouse is above the range box.
No reproduced in: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 39663a323c3330c18b610fcdc9e9c75ddac770f1 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Which operating system and VCL plugin?
Fedora Linux 38 KDE spin, kf5 (cairo+wayland)
Interestingly, I can reproduce with kf5 (cairo+xcb) in a recent trunk build: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 39663a323c3330c18b610fcdc9e9c75ddac770f1 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded The dialog keeps moving down until it touches the display's edge. But with kf5 (cairy+wayland) and gtk3, it only moves once to a different position to the one I set, but it stays there on subsequent opens.
No need to go through the Manage dialog, can be seen by repeatedly doing right-click > Conditional Formatting. Already reproduced in 6.4.0.3. No repro for gen VCL plugin.
(In reply to Stéphane Guillou (stragu) from comment #3) > Interestingly, I can reproduce with kf5 (cairo+xcb) in a recent trunk build: > > Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community > Build ID: 39663a323c3330c18b610fcdc9e9c75ddac770f1 > CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb) > Locale: en-AU (en_AU.UTF-8); UI: en-US > Calc: CL threaded > > The dialog keeps moving down until it touches the display's edge. This might be the same as tdf#137471. > But with kf5 (cairy+wayland) and gtk3, it only moves once to a different > position to the one I set, but it stays there on subsequent opens. This might be Wayland not allowing to access and control screen positions/coordinates by design.
(In reply to Michael Weghorn from comment #5) > This might be the same as tdf#137471. Closing as a duplicate of that bug. *** This bug has been marked as a duplicate of bug 137471 ***